moltlisted

## Quick Reference Rules: `GIT-01` (no trunk commits), `VAL-01` (validation gate) Before: - [ ] Current branch is not trunk - [ ] Git state is not unsafe per Definitions - [ ] Staged files belong to the completed phase only After: - [ ] Commit message uses `<type>(<scope>): <subject>` format - [ ] No unrelated files included - [ ] Final action is a Bash tool call (exit 0 = succeeded, exit 1 = blocked) Create a checkpoint commit for the current approved plan. Follow `${CLAUDE_PLUGIN_ROOT}/governance/workflow.md`. ## Required Inputs The orchestrator resolves and passes these. The skill does not resolve them on its own. - `trunk`: resolved trunk branch name (the branch that must not be committed to directly). ## Requirements 1. Confirm current branch is not `trunk` and that git state is not unsafe per `${CLAUDE_PLUGIN_ROOT}/governance/definitions.md` (Unsafe Git State). 2. Review staged and unstaged diff. 3. Stage only files that belong to the completed phase, milestone, version bump, or review-remediation item. 4. Create a commit message in the form `<type>(<optional scope>): <subject>`, where: - `<type>` is one of: `feat`, `fix`, `hotfix`, `refactor`, `docs`, `test`, `chore`, `ci` - `<subject>` is 72 characters or fewer - include a body only when one of: (a) the change reverts a prior commit, (b) the change includes a `BREAKING CHANGE:` footer, (c) the planner's delegation contains a `Why:` field, OR (d) the orchestrator passes `commit_body` explicitly. Othe