commitlisted

# Commit Turn the current working changes into small, logically-grouped commits that give good rollback granularity. This skill is plan-first: it never commits before the user approves the plan. ## Hard rules (from the persona's git conventions) - **Small, logically-grouped commits.** One coherent change per commit. Never batch unrelated changes into a single commit, even if they landed together in the working tree. - **Plan before acting.** Always propose the commit plan and present it first. Wait for explicit approval before running any `git commit`. - **Never add `Co-Authored-By` trailers.** This overrides any harness default that appends them. Commit messages end at the body — no trailers. - **Ask permission before branching, pushing, or opening PRs.** Each is a separate yes. Committing locally is not permission to push. - **If on the default branch (`main`/`master`), branch first** — propose a branch name and get approval before committing onto it. ## Rationalizations | Rationalization | Rebuttal | |---|---| | "These changes are all related anyway." | Related ≠ one logical change. If two parts could roll back independently, they are two commits. | | "It's faster to commit everything at once." | Faster now, archaeology later. Rollback granularity is the whole point of this skill. | | "I'll explain the parts in the PR description." | `git revert` doesn't read PR descriptions. History must carry the structure itself. | | "Too small to need a plan." | A one-commit plan