Agent skill
repo:commit
Kagenti commit message format - emoji prefixes, sign-off, and conventions
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/repo-commit
SKILL.md
Kagenti Commit Conventions
Format
<emoji> <Short descriptive message>
<Optional longer description>
Signed-off-by: <Name> <email>
Co-authored-by: Claude <[email protected]>
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
🌱 Add E2E testing infrastructure and deployment health tests
Implements initial end-to-end testing framework for Kagenti platform.
Signed-off-by: Developer <[email protected]>
Co-authored-by: Claude <[email protected]>
🐛 Fix VPC cleanup order: delete subnets before route tables
Signed-off-by: Developer <[email protected]>
Sign All Commits
After rebase or if commits are unsigned:
git rebase --signoff HEAD~$(git rev-list --count upstream/main..HEAD)
Related Skills
git:commit- Git commit mechanicsrepo:pr- PR creation conventionstdd:ci- TDD commit step
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?