| name | commit |
| description | Generates commit messages and creates commits. Use when writing commit messages, committing changes, or reviewing staged changes. |
Commit Messages
Use Conventional Commits format.
Format
<type>(<scope>): <description>
[optional body]
Types
feat: User-facing features or behavior changes (must change production code)fix: Bug fixes (must change production code)docs: Documentation onlystyle: Code style/formatting (no logic changes)refactor: Code restructuring without behavior changetest: Adding or updating testschore: CI/CD, tooling, dependency bumps, configs (no production code)
Scopes
Optional. Use when it adds clarity. Examples: fetch, extract, checks, sources, facts, notify, config.
Examples
feat(sources): add theflip.museum hours scraper
fix(normalize): treat "St" and "Street" as equal
refactor(checks): split observation from assertion
chore: bump ruff to latest
docs: document the structured-data corroboration rule
test: assert STRUCTURE_CHANGED when the hours anchor is removed
Instructions
- Run
git diff --staged to see staged changes
- Analyze the changes and determine the appropriate type
- Write a concise description (under 72 characters)
- Add body only if the "why" isn't obvious from the description
