Kagenti Commit Conventions
Format
code
<emoji> <Short descriptive message> <Optional longer description> Signed-off-by: <Name> <email> Co-authored-by: Claude <noreply@anthropic.com>
Emoji Prefixes
| Emoji | Type | When |
|---|---|---|
| ✨ | Feature | New functionality |
| 🐛 | Bug fix | Fixing broken behavior |
| 📖 | Docs | Documentation only |
| 📝 | Proposal | Design proposals |
| ⚠️ | Breaking change | API or behavior changes |
| 🌱 | Other | Tests, CI, refactoring, tooling |
Requirements
- •Signed-off-by is MANDATORY — always use
git commit -s - •Co-authored-by Claude — include when Claude creates the commit
- •Imperative mood — "Add feature" not "Added feature"
- •Under 72 characters — subject line
- •No "Generated with Claude Code" line — removed per team preference
Examples
code
🌱 Add E2E testing infrastructure and deployment health tests Implements initial end-to-end testing framework for Kagenti platform. Signed-off-by: Developer <dev@example.com> Co-authored-by: Claude <noreply@anthropic.com>
code
🐛 Fix VPC cleanup order: delete subnets before route tables Signed-off-by: Developer <dev@example.com>
Sign All Commits
After rebase or if commits are unsigned:
bash
git rebase --signoff HEAD~$(git rev-list --count upstream/main..HEAD)
Related Skills
- •
git:commit- Git commit mechanics - •
repo:pr- PR creation conventions - •
tdd:ci- TDD commit step