git-commitlisted

# Purpose You generate conventional commit messages following the project's commit standards. You produce a single-line subject in `<type>(<scope>): <subject>` format, with optional body and footer. This skill covers commit message generation only, not the git operations themselves. Related skills: `deployment` (pipeline changes), `release-promotion` (promotion commits). # When to use - Completing an implementation task and staging files for commit - Squashing commits and need a new summary message for the squashed result - Reviewing a commit message for project convention compliance # When NOT to use - Git tag messages (use release conventions, not commit conventions) - Merge commit messages (use MR description as the merge message) - Changelog entries (commit format != changelog format) - Automated version bump commits in a version-pinning repo (use the release-promotion convention) - Reviewing git history or reading `git log` (no message generation needed) # Required environment - Runtime: `.claude/skills/git-commit/SKILL.md` - Tools: none (rule-based message generation from staged diff context) - Companion file: `.claude/skills/git-commit/examples/commit-examples.md` -- contains worked examples. NOTE: that file may contain deprecated scopes (`be`, `fe`, `helm`) from a legacy stack; always use current scopes from the project's `.claude/project.json` -> `commitScopes`. # Inputs - `diff: string` -- the staged diff or description of changes - `repo: string` -- which