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:
Install
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://github.com/obra/superpowers/blob/main/skills/finishing-a-development-branch/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.