Git Finish

Own the work until the PR is ready to merge. Finish the implementation, satisfy its definition of done, review it locally, publish it, and keep working through CI and reviewer feedback. A pushed branch, an open PR, or a pending review is an intermediate state.

Compose the existing skills rather than replacing their mechanics:

• singular-code-review for local review and evidence-backed findings.
• git-commit-pr for commit boundaries, staging, validation, and PR preparation.
• git-fix-pr for blocker triage, reviewer replies, thread resolution, and batched follow-up pushes.
• gh-stack when managing dependent branches and PRs.

Read each skill before its phase. Resolve it from the available skill catalog, sibling skill directories, or the repository that supplies it. If a required skill is missing, identify the missing dependency and the phase it prevents; do not silently substitute a partial workflow.

Establish Scope And Authority

Recover the original request, conversation decisions, applicable repository instructions, local TODO.md / PLAN.md, linked specifications or tickets, and any existing PR discussion. Establish the repository, worktree, branch, intended base, owned changes, and existing PR or stack before editing or publishing. Resume existing work instead of creating duplicate PRs.

Explicit user invocation of this skill requests the complete lifecycle for the assigned work: implementation, review fixes, commits, pushes, PR creation or updates, marking ready, and reviewer replies/resolution. An explicitly delegated invocation inherits only the authority and scope the parent actually received and passed on. Carry that authorization into the component skills: their routine planning and publish confirmations are already answered for this work. Show concise decisions and progress, then proceed.