# <type>(<scope>): <subject>
#
# <body>
#
# <footer>

# Type should be one of the following:
# * feat: A new feature
# * fix: A bug fix
# * docs: Documentation only changes
# * style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
# * refactor: A code change that neither fixes a bug nor adds a feature
# * perf: A code change that improves performance
# * test: Adding missing tests or correcting existing tests
# * chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
#
# Scope should be the area of the codebase affected (optional)
# Subject should be a short description of the change
# Body should provide more detailed information about the change
# Footer should contain any information about Breaking Changes and reference issues that this commit closes
#
# Examples:
# feat(mcp): add new search tools for financial data
# fix(api): resolve authentication error in client
# docs: update installation instructions
# test: add unit tests for MCP server
# chore: update dependencies
