Finish a development change safely by inspecting the final tree, verifying at the right scope, and performing only the requested Git or PR actions.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Close the work without turning completion into an automatic merge ritual.
Check:
git status --shortDo not modify or discard unrelated changes.
When replacement is complete, remove the superseded path in the same change. Retain compatibility only for an evidenced current caller or staged boundary, and name the reason and removal condition; an inert parallel implementation is not a rollback plan.
Map the final implementation to the requested behavior:
Do this once. Do not reopen accepted design decisions without evidence. Treat implementation deviations as evidence to review, not as authority that settles product meaning. Before integration, require applicable approval for any change to programme order, trust boundaries, or accepted product scope.
Use a risk-matched verification ladder:
Run checks after the final relevant edit. State exactly what passed and what was not run.
Perform a compact self-review for:
For high-risk work, one independent reviewer can add value. Verify that reviewer’s findings yourself. Do not require duplicate reviewers for ordinary changes.
Update durable documentation when the change affects:
Do not add changelog noise for invisible local refactors unless repository policy requires it.
Close the existing task record with actual results, evidence and remaining unverified scope. Distinguish completed, paused, cancelled and superseded work; link a successor when replaced. Move lasting usage or architecture facts into their maintained documentation and link them from the plan. Do not turn historical plans into live runbooks or delete them in bulk.
Only commit, push, merge, or create a PR when the user requests that action or applicable repository/global instructions delegate it.
When committing:
git add ..When preparing a PR:
When work remains local, report the branch and workspace path.
For workspace cleanup, read and apply the Worktree method’s shared removal and authorization contract before acting. From the router use references/worktree.md; from the explicit finish leaf use ../worktree/SKILL.md. Incidental cleanup covers only this workflow’s resources; an explicit request can also select pre-existing worktrees. Present exact targets and actions, protect ignored/local data and current tips, recheck each candidate immediately before removal, and verify preserved refs afterward. Existing authorization for the exact batch is sufficient; do not request it again.
Parking may remove an unmerged checkout while preserving a durable named ref and restoration route. Removing a checkout does not authorize deleting its branch, discarding data, or pruning registrations. Deletion of branches, changes, generated data, or stashes requires explicit authority for that action. Respect active tasks, locks, and the host’s lifecycle; use supported host cleanup for host-managed worktrees. Leave uncertain items pending while completing independent authorized items.
Provide:
Keep it compact and factual.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Investigate and fix bugs, failing tests, regressions, build failures, or unexpected behavior using boundary localization, evidence, and bounded hypotheses.
The English summary is being prepared. Showing the original description.
Choose responsibility for substantial work before deep execution: keep one responsibility's coupled parts in a single lane, and hand a bounded or independent lane to a worker when clean context, an unknown cause, independent review, or coordinator attention materially improves the outcome.
The English summary is being prepared. Showing the original description.
Turn a rough feature, product interaction, or architecture idea into a concrete design. Use when meaningful decisions remain open; avoid for already-clear local edits.
The English summary is being prepared. Showing the original description.
Implement a settled request or current execution strategy through connected slices, feed observations into the same task record, and revise affected work when evidence changes.
The English summary is being prepared. Showing the original description.
Assess, adapt, and apply specified discussions, feedback, findings, or references to existing project work. Preserve coverage, corrections, and selected intent; judge fit and carry adopted effects through the authorized result. Includes technical review feedback; incidental sources or understanding material without a target-work adoption question need no separate incorporation workflow.
The English summary is being prepared. Showing the original description.
Form and maintain execution strategy when order, effort, evidence timing or recovery materially affects the outcome, even with a settled goal. Reuse durable task records when continuity needs them; keep clear work direct.
The English summary is being prepared. Showing the original description.