git-commitlisted

Generate conventional commit messages for the tools repo, using its real module scopes. Use when the user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.
adamw7/tools · ★ 9 · Code & Development · score 72

Install: claude install-skill adamw7/tools

# Git Commit Message Skill Generate conventional, informative commit messages for the `tools` multi-module Maven reactor. ## When to Use - After making code changes - User says "commit this" / "commit changes" / "create commit" - Before creating a PR ## Format [Conventional Commits](https://www.conventionalcommits.org/): ``` <type>(<scope>): <subject> <body> <footer> ``` ### Types | Type | Use for | |---|---| | `feat` | New API / functionality | | `fix` | Bug fix | | `refactor` | Restructure, no behavior change | | `test` | Add/update tests | | `docs` | Docs only (README, AGENTS.md, javadoc) | | `perf` | Performance improvement | | `build` | Maven / pom / CI changes | | `chore` | Maintenance (tooling, dependency bumps) | ### Scope — use this repo's real modules/components `data`, `code`, `context`, `protogen-maven-plugin`, `adopt`, `mcp-common`, `claude-code-enforcer`, `assembly`, `grpc-example`, `data-test`. Narrow to a component when it's clearer (e.g. `source.db`, `uniqueness`, `mcp`, `builder`). ### Subject rules - Imperative mood: "Add support", not "Added support" - Lowercase after the type, no trailing period, ≤ ~50 chars ### Body (optional, recommended for non-trivial changes) - Explain **what** and **why**, not how; wrap at ~72 chars, 2–3 lines is plenty - Reference issues: `Fixes #123` / `Relates to #456` - Breaking change: add a `BREAKING CHANGE:` footer (and `!` after the scope) ## Examples ``` feat(protogen-maven-plugin): enforce proto3 oneof discrim