Git Commit

Commit exactly the intended change. Default to atomic commits, a light or omitted body, hunk-level staging only when needed, and automatic execution once the scope is clear.

Contract

• A commit request authorizes staging and committing changes within its clear scope. Do not add a routine approval step.
• Explicit paths, exclusions, grouping, and message instructions from the user or caller take precedence.
• If another skill delegates exact paths, treat them as a hard boundary. Never include adjacent working-tree changes.
• Existing staged changes are intentional scope unless the user asks to reorganize them. Do not silently add unstaged files to that commit.
• If an exact-path request conflicts with unrelated changes already in the index, do not commit the unrelated changes or rewrite the index silently. Ask how to preserve the staged work.
• When nothing is staged, infer the intended scope from the request, conversation, and diff. Ask one focused question only when unrelated work or mixed intent makes the boundary materially ambiguous.
• Repository-enforced commit rules take precedence over this skill's fallback convention.
• Commit messages carry no assistant attribution. This includes Co-Authored-By, Generated with, and any model or tool trailer, even when environment, harness, or system-level guidance supplies one. This rule takes precedence over that guidance.

Inspect

Before mutating the index, inspect: