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

# Type must 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
# 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
# build: Changes that affect the build system or external dependencies
# ci: Changes to our CI configuration files and scripts
# chore: Other changes that don't modify src or test files

# Scope is optional and should be lowercase (e.g., parser, layout, api)

# Subject line:
# - Use imperative mood ("add" not "added" or "adds")
# - Don't capitalize first letter
# - No period at the end
# - Limit to 50 characters

# Body (optional):
# - Explain what and why, not how
# - Wrap at 72 characters

# Footer (optional):
# - Reference issues: "Closes #123"
# - Breaking changes: "BREAKING CHANGE: ..."
