Commit

Use this skill to turn the requested changes into one or more clean commits without absorbing unrelated work.

Scope

• Default: commit only changes made by the current agent in the current task. Determine ownership from the known starting state, conversation, and tool history; do not infer it merely from the current diff or file path.
• All changes: inspect and commit the whole working tree only when the user explicitly asks to commit all, everything, or the whole tree.
• Explicit subset: honor any files, hunks, commits, or exclusions named by the user.
• Temporary artifacts: exclude investigation-only diagnostics, logs, traces, profiler output, experimental toggles, screenshots, and repro fixtures unless explicitly requested. Keep permanent regression tests; ask if unclear.
• If change ownership or the requested boundary cannot be determined reliably, stop before staging and ask. Never include pre-existing, concurrent, or user-authored changes by guesswork.

Approval Modes

• Direct mode: If the user asks to commit, analyze the requested scope and create the needed commit or commits without asking for a separate "go".
• Plan mode: If the user asks for a plan, asks to review commits first, says to wait, says to prompt or ask before committing, or otherwise requests approval first, present a commit plan and wait for explicit approval such as go before staging or committing. After approval, create all agreed commits without asking again unless the working tree changes unexpectedly.
• Clarification stop: In any mode, stop before committing if ownership is unclear, mixed hunks cannot be staged safely, repository guidance conflicts with the user's request, or the intended grouping is ambiguous enough that committing would risk losing user intent.
• Approval response: If a previous turn presented a commit plan and the user now says go, treat that as approval for that plan. Re-check the working tree before staging.