Agent skill
Generating JJ Commit Messages
Generate descriptive commit messages for jujutsu repositories. Use when creating commits, describing changes, or when the user asks for commit message help. Follows conventional commit format and project conventions.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/generating-jj-commit-messages
SKILL.md
Generating JJ Commit Messages
Format
Summary line: type(scope): brief description (under 72 chars)
Body (optional): Blank line, then detailed explanation with bullets
Footer:
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Conventional Commit Types
| Type | Use Case | Example |
|---|---|---|
| feat | New features | feat(auth): implement JWT authentication |
| fix | Bug fixes | fix(login): correct password validation |
| refactor | Code restructuring | refactor(auth): extract token helper |
| docs | Documentation | docs(api): update auth examples |
| test | Tests | test(auth): add login flow tests |
| chore | Maintenance | chore(deps): upgrade to Python 3.12 |
| style | Formatting | style(auth): format with black |
| perf | Performance | perf(db): optimize query with index |
| ci | CI/CD | ci: add automated testing workflow |
| build | Build system | build(nix): update flake inputs |
Quick Guidelines
- Use imperative mood: "Add" not "Added"
- Be specific: "Fix memory leak in parser" not "Fix bug"
- Scope is optional but helpful:
feat(auth): ...or justfeat: ... - Keep summary under 72 characters
- Add body with bullets for complex changes
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?