How do I install the Finish Worktree skill?

Run npx skillmds@latest add majiayu000/finish-worktree in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Finish Worktree skill do?

After an issue's PR has squash-merged on GitHub and its issue has closed: fast-forward the default branch, remove the issue-numbered nested worktree (.worktrees/ ), and delete the local feature branch. Use when the user says to finish, tear down, or clean up a lane or worktree for a merged issue. It is listed under Coding & Dev Tools on SkillMD.

Is Finish Worktree safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Finish Worktree?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Finish Worktree free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Finish Worktree?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Finish Worktree by majiayu000 — Agent Skill

Name: Finish Worktree
Rating: 4.2 (5 reviews)
Author: majiayu000

Finish Worktree

After an issue's PR has squash-merged on GitHub and its issue has closed: fast-forward the default branch, remove the issue-numbered nested worktree (.worktrees/<issue#>), and delete the local feature branch. Use when the user says to finish, tear down, or clean up a lane or worktree for a merged issue.

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

Finish-Worktree

Teardown counterpart to /move-to-worktree. Run it in the primary checkout, on the default branch, after you squash-and-merge the issue's PR on github.com. The script uses GitHub's PR and issue state as the authoritative merge guard; remote branch deletion is an additional safety check, not proof of merge by itself.

Run (1 bash call)

bash {base_directory}/finish-worktree.sh <issue-number>

The script:

Hard-stops unless run in the clean primary checkout on the default branch.
Finds exactly one local branch {type}/<issue#>/{slug} and its matching worktree.
Uses gh to verify a PR for that exact head branch is merged, its recorded head commit matches the local branch tip, and issue <issue#> is closed. It also requires the remote feature branch to be gone.
git pull --ff-only on the default branch (brings the squashed work in) + git fetch --prune (clears the stale tracking ref).
git worktree remove .worktrees/<issue#> — never --force: if the worktree has uncommitted work it prints the leftovers and stops.
git branch -D <branch> — capital -D is deliberate: squash-merge means git can't prove the branch merged, so -d always refuses; step 3 already verified the work landed.

Non-zero exit → hard-stop, print stderr verbatim.

Report

What was removed (worktree path, branch), then the standing post-merge hygiene reminder: run /archive-issue <issue#> promptly to retire the issue's specs/ artifacts to the wiki. After any merge, in-flight lanes should sync with the default branch only when they need the merged work; for an already pushed/shared lane, merge the default branch rather than rewriting its history.

You Must NOT

Use git worktree remove --force or otherwise discard uncommitted work — surface it and stop.
Delete the branch when any merge guard fails.
Archive the issue yourself unless asked — remind, don't perform.

---name: finish-worktreedescription: After an issue's PR has squash-merged on GitHub and its issue has closed: fast-forward the default branch, remove the issue-numbered nested worktree (.worktrees/<issue#>), and delete the local feature branch. Use when the user says to finish, tear down, or clean up a lane or worktree for a merged issue.--- # Finish-Worktree Teardown counterpart to `/move-to-worktree`. Run it **in the primary checkout, on the default branch**, after you squash-and-merge the issue's PR on github.com. The script uses GitHub's PR and issue state as the authoritative merge guard; remote branch deletion is an additional safety check, not proof of merge by itself. ## Run (1 bash call) ```bash bash {base_directory}/finish-worktree.sh <issue-number> ``` The script: 1. Hard-stops unless run in the clean primary checkout on the default branch. 2. Finds exactly one local branch `{type}/<issue#>/{slug}` and its matching worktree. 3. Uses `gh` to verify a PR for that exact head branch is **merged**, its recorded head commit matches the local branch tip, and issue `<issue#>` is **closed**. It also requires the remote feature branch to be gone. 4. `git pull --ff-only` on the default branch (brings the squashed work in) + `git fetch --prune` (clears the stale tracking ref). 5. `git worktree remove .worktrees/<issue#>` — **never `--force`**: if the worktree has uncommitted work it prints the leftovers and stops. 6. `git branch -D <branch>` — capital `-D` is deliberate: squash-merge means git can't prove the branch merged, so `-d` always refuses; step 3 already verified the work landed. Non-zero exit → hard-stop, print stderr verbatim. ## Report What was removed (worktree path, branch), then the standing post-merge hygiene reminder: run `/archive-issue <issue#>` promptly to retire the issue's `specs/` artifacts to the wiki. After any merge, in-flight lanes should sync with the default branch only when they need the merged work; for an already pushed/shared lane, merge the default branch rather than rewriting its history. ## You Must NOT - Use `git worktree remove --force` or otherwise discard uncommitted work — surface it and stop. - Delete the branch when any merge guard fails. - Archive the issue yourself unless asked — remind, don't perform.

Frequently asked questions