Defame1297
ae791781c2
git-workflow calls itself a router but named two of the six domains it routes to; the other four appeared nowhere in the file. All six are now named, with a routing table in the always-loaded body. git-submodules lost the foreach shell-variable semantics -- only the bare names survived, though $sm_path and $displaypath differ solely by which directory you are in. The table is back. Its relocated commands had also dropped the rtk git prefix its own SKILL.md mandates; 24 of them are re-prefixed. The wider rtk inconsistency across the plugin stays with #113. Also restores git-commits' body and footers output fields, git-branches' tag/ branch detection commands, git-worktrees' git config --worktree, pc-run's ambiguity fallback, git-remotes' git-history boundary, and git-history's pickaxe triggers. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EJJrm5YmacbwMdzZpXcoti
git-commits
Create, amend, squash, and cherry-pick commits with Conventional Commits formatting and validation.
What it does
This skill handles commit operations within the git workflow suite. It generates well-formatted commit messages following the Conventional Commits spec, validates against commitlint config-conventional constraints, and communicates SemVer impact. It enforces confirmation gates for history-altering operations (amend, rebase, squash) and returns structured JSON output for agent consumption.
Usage
/git-commits
Describe your commit task: create a new commit, amend, squash, or cherry-pick. The skill will guide message formatting and handle confirmation for destructive operations.
Files
| File | Loaded when |
|---|---|
SKILL.md |
Always — gotchas, the flow dispatch table, the gates common to every flow, and the output shape |
references/create-commit.md |
Composing a new commit from staged changes |
references/rewrite-history.md |
Amending, squashing, or folding a fixup!/squash! commit into an earlier one |
references/cherry-pick.md |
Replaying an existing commit onto the current branch |
references/conventional-commits-spec.md |
A type, footer, or breaking-change edge case is not obvious — full spec, 11-type set, commitlint constraint table |
references/commit-template.md |
Writing a body for a non-trivial commit — Why / Implementation Notes / Impact structure and the full trailer list |
references/sources.md |
Research sources and provenance |
Composition
Part of the git plugin's domain suite. This skill owns commit authoring and history-rewriting operations only; git-history inspects history, git-branches owns branch lifecycle, and git-workflow is the conversational entry point that routes between them.