commitlisted

# Commit ## Iron Law `COMMIT ONLY THE REVIEWED SLICE. STAGE FILES BY NAME.` The host owns git invocation; this skill sets the packaging standard. ## When to Use - The user asks to commit, stage, split, or package current changes. - Dirty files need grouping into logical commits, or a commit needs a subject and body. ## When NOT to Use - Branches, conflicts, rebases, recovery, force-push, GitHub; use `git-workflow`. - Reviewing the diff; use `code-review` first for non-trivial work. - Versions, changelogs, tags, publishing; use `release` when approved. ## Rules 1. Check the tree state first and stop on anything unexpected: wrong branch, unresolved merge state, files you do not recognize. 2. A branch is not the commit boundary. Group changes by behavior so one behavior can be reverted without dragging unrelated work. Nearby work that would need a different rollback decision waits for its own commit. 3. Stage only named files or approved pathspecs for the reviewed slice. Never `git add .` in a messy tree. Confirm the staged diff matches the slice. Unrelated dirty or untracked files stay unstaged and are named as deferred. 4. Confirm the relevant proof is current before committing. If a broad suite is noisy for unrelated reasons, name the targeted proof and report the drift separately. 5. The subject completes "When applied, this commit will ...". Add a body only when the change needs context, at most 2-3 short paragraphs. 6. Attribution tr