Finishing a Development Branch
Close out a development branch safely: verify tests, detect worktree state, present integration options, execute, clean up
- What
- Close out a development branch safely: verify tests, detect worktree state, present integration options, execute, clean up
- Cost
- Free
- Needs
- a git repository to work in; git CLI available. Companion superpowers skills (writing-plans, subagent-driven-development) for the full workflow.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — an end-of-branch workflow for agents: verify the full test suite is green, detect the environment (normal repo, named-branch worktree, or detached HEAD), confirm the base branch, then present the integration menu — merge locally, push and open a pull request, or keep the branch as-is — and only the human decides; discarding is gated behind an explicit `discard` confirmation, and worktree cleanup is provenance-based (it never `--force`s a removal that would destroy uncommitted files, it shows you what's at stake and asks). A table of "common rationalizations" punctures the classic shortcuts: a green run only proves the tree it ran on, integration is never assumed, and a rejected push means the remote moved. By @obra, listed here with credit to its creator. Honest caveats: it runs real git commands with real consequences (merges, branch deletion, worktree removal) — the gates are the safety, so review each step before approving; it expects worktrees created by the superpowers convention when cleanup ownership matters. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Finishing a Development Branch is a free Muse skill for closing out a development branch safely. It verifies the test suite is green, detects the environment such as a normal repo, named-branch worktree or detached HEAD, confirms the base branch, then presents options like merge locally, push with a pull request, or keep the branch, with only the human deciding.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit bb92a77Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a git repository to work in; git CLI available. Companion superpowers skills (writing-plans, subagent-driven-development) for the full workflow. Install "Finishing a Development Branch" for me. It safely closes out a development branch: verify tests, detect worktree state, present the merge/PR/keep menu, execute the human's choice, and clean up. Repository: https://raw.githubusercontent.com/obra/superpowers/bb92a77741419a4ab5f06e711a283343f1ada0c3/skills/finishing-a-development-branch/SKILL.md Pinned version: install the code at commit bb92a77741419a4ab5f06e711a283343f1ada0c3 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "obra-finishing-a-development-branch". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- bb92a77 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.