Commit Standards
MangroveAI uses Conventional Commits. A Huskycommit-msg hook enforces compliance automatically.
Format
Valid Types
| Type | Description | Example |
|---|---|---|
feat | New feature | feat(ai-copilot): add state machine integration |
fix | Bug fix | fix(backtesting): resolve calculation error |
docs | Documentation | docs(readme): update setup instructions |
style | Formatting | style: format code with black |
refactor | Code restructure | refactor(strategies): reorganize strategy loader |
perf | Performance | perf(database): optimize query performance |
test | Tests | test(api): add integration tests |
chore | Build/tooling | chore: update dependencies |
ci | CI/CD changes | ci: fix commitlint workflow |
revert | Revert commit | revert: revert previous feature |
Common Scopes
Domain Scopes
ai-copilot, backtesting, strategies, signals, positions, crypto-assets, auth
Infrastructure Scopes
docker, ci, config, api, database, tests, docs
Rules
- Type and subject are required; scope is optional
- Subject must be lowercase and not end with a period
- Use imperative mood: “add feature” not “added feature”
- Keep the subject line under 72 characters
- Use the body for detailed explanations when needed