commit

name	commit
description	Use when the user explicitly authorizes Git or publication actions: verify repository state, then commit, push, open a pull request, tag, release, or deploy only as authorized.
argument-hint	[request or context]

Contextual selection

CoderKit is an optional helper framework, not a mandatory process. Self-select this workflow when the current request clearly matches its purpose and the added structure will materially improve a substantive development task. Never ask the user whether to activate CoderKit or whether to use CoderKit instead of normal host behavior: workflow selection is an internal execution decision, not a user decision.

Skip CoderKit for simple questions, routine commands, obvious one-line edits, or work whose outcome and path are already clear. Select only the smallest useful workflow; do not run the full explore → plan → implement → verify → commit sequence as ceremony. When no workflow adds enough value to justify its overhead, continue with normal host behavior.

Ask only when the outcome, scope, or required authority is materially unclear; never ask merely to choose or confirm a workflow. Automatic selection does not expand the user's authority or permit adjacent work.

Prompting envelope

Structure the work in this order:

• Outcome: state the result the user wants before choosing an approach.
• Relevant context: gather what the prompt, repository, and named artifacts already provide before asking for anything.
• Important boundaries: identify the scope, authority, and constraints the work must not cross.
• Work: execute against the outcome within those boundaries.
• Verification: prove the outcome with the completion evidence this tool requires.

Ask only when missing information materially changes the result or required authority. Accept steering without restarting the workflow.

Proportionality

Right-size the workflow to the task. Use a fast path when the outcome and evidence are obvious; use deeper investigation only when uncertainty, risk, or scope warrants it. Do not create documents, dispatch agents, add process infrastructure, or expand test coverage merely because the workflow can — the work artifacts below are the one exception: they are mandated completion evidence, not discretionary documents. Stop when the completion evidence is satisfied. A finished, verified result is better than a perfect process.

Treat user-named files, URLs, tools, and prior artifacts as authoritative inputs: inspect them before substituting a generic alternative. Keep tangential cleanup and speculative improvements out of the active scope unless the user asks for them.

Work artifacts

Persistent work products live in the target project under docs/work/NNN-short-name/: NNN is a zero-padded index allocated as the highest existing index plus one (starting at 000), and short-name is a kebab-case name derived from the request.

• plan.md — written by plan whenever it runs; the stable contract later tools read as authority.
• tasks.md — created and maintained by implement from the plan's units: main tasks, subtasks, and any subagent or orchestration assignments, with statuses updated as work progresses.
• tasks/ — optional subfolder, created only when a single task needs a dedicated brief (for example a subagent fan-out).

Explore produces no artifact. Tools other than plan and implement read these files but do not create them.

Completion

Finish with the evidence required by this tool. Select another CoderKit workflow only when it is genuinely needed and the user's existing request already authorizes that work; never chain the whole lifecycle by default. Otherwise stop and report the result or natural next step without asking the user to activate anything. Never turn workflow selection into a confirmation prompt, and never treat automatic selection as authorization for Git publication, deployment, destructive changes, or other adjacent work.

Commit

Method

1. Resolve the requested mode: commit only, push, pull request, description update, tag, release, deploy, or a combination. Do not broaden one mode into another.
2. Inspect status, unstaged and staged diffs, current branch, remote default branch, upstream relationship, existing pull request, and release state.
3. Confirm the exact target and authorization for externally visible actions. A direct request to ship is authority for the named actions, not for adjacent publication.
4. Match repository conventions for branch names, commit messages, pull-request titles, and release notes. Create a feature branch when project policy requires one; honor an explicit request to publish the default branch.
5. Run the agreed proportional checks and stop on material failure. Do not rerun unrelated suites merely to increase confidence cosmetically.
6. Stage explicit intended paths, inspect the staged diff, and group only genuinely distinct concerns into separate commits. Avoid broad staging that can capture secrets or unrelated files.
7. Push, create or update the pull request, tag, release, or deploy within the authorized scope. Preserve existing issue links and useful PR context.
8. Verify remote state after mutation: commit SHA, branch/upstream, PR URL and status, tag, release, deployment, and working-tree cleanliness.

Guardrails

• Never claim publication from a local commit alone.
• Never invent screenshots, test evidence, issue links, or deployment success.
• If credentials or policy block one requested action, complete safe independent actions and report the exact blocker.

Completion evidence

Exact verification, Git, hosting, or release state produced.