New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Superpowers Finishing A Development Branch

by christopherarter in christopherarter/superpowers-reasonix

Branch finished, tests green?. An agent skill from christopherarter/superpowers-reasonix.

MITAuto-check passedDevelopment

Install Superpowers Finishing A Development Branch

skills CLI
$ npx skills add christopherarter/superpowers-reasonix --skill superpowers-finishing-a-development-branch -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install christopherarter/superpowers-reasonix superpowers-finishing-a-development-branch --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/christopherarter/superpowers-reasonix.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/superpowers-finishing-a-development-branch .claude/skills/superpowers-finishing-a-development-branch && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
superpowers-finishing-a-development-branch
GitHub stars
102
Token cost
~1.3k tokens
SKILL.md length
463 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Branch finished, tests green?. An agent skill from christopherarter/superpowers-reasonix.

  • Works in 6 steps: Verify Tests → Detect Environment → Determine Base Branch → …
  • Tasks that involve Git worktrees
  • SKILL.md covers Overview, The Process, Quick Reference and Red Flags
  • Calls git, npm and gh

What it does

Superpowers Finishing A Development Branch is an agent skill from christopherarter/superpowers-reasonix. Branch finished, tests green? Load first to merge, PR, or clean up.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git worktrees. It works with Git. The repository describes itself as: Superpowers skill port to Reasonix coding harness. The licence is MIT.

When your agent uses it

  • Tasks that involve Git worktrees

Example prompts

  • “/superpowers-finishing-a-development-branch”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Verify Tests
  2. Detect Environment
  3. Determine Base Branch
  4. Present Options
  5. Execute Choice
  6. Cleanup Workspace

What it can do on your machine

Read from SKILL.md and the folder at commit d202ba4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • npm
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, npm and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Superpowers Finishing A Development Branch loads about 1.3k tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 463 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~28
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from christopherarter/superpowers-reasonix at commit d202ba4, republished under its MIT licence (© christopherarter). 463 words, ~1,261 tokens.

Download SKILL.mdSave it as .claude/skills/superpowers-finishing-a-development-branch/SKILL.md (or your agent's skills folder).
name
superpowers-finishing-a-development-branch
description
Branch finished, tests green? Load first to merge, PR, or clean up.

Finishing a Development Branch

Overview

Present clear options. Handle chosen workflow.

Core principle: Verify tests → detect environment → present options → execute choice → clean up.

Announce at start: "I'm using the superpowers-finishing-a-development-branch skill to complete this work."

The Process

Step 1: Verify Tests

Verify tests pass before options (use superpowers-verification-before-completion):

bash
npm test / cargo test / pytest / go test ./...

Tests fail: report failures. Cannot merge/PR until they pass. Stop. Tests pass: continue.

Step 2: Detect Environment

Capture all three up front, before any later step changes directory — WORKTREE_PATH must reflect where you are now, not after Step 5 has cd'd to the main repo root:

bash
GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)
GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)
WORKTREE_PATH=$(git rev-parse --show-toplevel)
StateMenuCleanup
GIT_DIR == GIT_COMMON (normal repo)Standard 4 optionsNo worktree to clean up
GIT_DIR != GIT_COMMON, named branchStandard 4 optionsProvenance-based (Step 6)
GIT_DIR != GIT_COMMON, detached HEADReduced 3 options (no merge)No cleanup (externally managed)
Step 3: Determine Base Branch
bash
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null

Or ask: "Branch split from main — correct?"

Step 4: Present Options

Normal repo or named-branch worktree — present exactly these 4 options:

Implementation complete. What would you like to do?

1. Merge back to <base-branch> locally
2. Push and create a Pull Request
3. Keep the branch as-is (I'll handle it later)
4. Discard this work

Which option?

Detached HEAD — present exactly these 3 options:

Implementation complete. You're on a detached HEAD (externally managed workspace).

1. Push as new branch and create a Pull Request
2. Keep as-is (I'll handle it later)
3. Discard this work

Which option?

Don't add explanation. Keep options concise.

Step 5: Execute Choice
Option 1: Merge Locally
bash
MAIN_ROOT=$(git -C "$(git rev-parse --git-common-dir)/.." rev-parse --show-toplevel)
cd "$MAIN_ROOT"
git checkout <base-branch>
git pull
git merge <feature-branch>
<test command>   # Verify tests on merged result

After merge succeeds: cleanup worktree (Step 6), then git branch -d <feature-branch>.

Option 2: Push and Create PR
bash
git push -u origin <feature-branch>
gh pr create --title "<title>" --body "$(cat <<'EOF'
## Summary
<2-3 bullets of what changed>

## Test Plan
- [ ] <verification steps>
EOF
)"

Do NOT clean up the worktree — needed alive for PR feedback.

Option 3: Keep As-Is

Report: "Keeping branch <name>. Worktree preserved at <path>." No cleanup.

Option 4: Discard

Confirm first — require typed discard:

This will permanently delete:
- Branch <name>
- All commits: <commit-list>
- Worktree at <path>

Type 'discard' to confirm.

Confirmed: cd to main repo root, cleanup worktree (Step 6), then git branch -D <feature-branch>.

Show full SKILL.md (218 more words)Show less
Step 6: Cleanup Workspace

Runs for Options 1 and 4 only. Options 2 and 3 preserve worktree.

Reuse the GIT_DIR, GIT_COMMON, and WORKTREE_PATH captured in Step 2 — do NOT recompute them here. Step 5 (Options 1 and 4) has already cd'd to the main repo root, so a fresh git rev-parse --show-toplevel would return the main repo, not the worktree, and remove the wrong path. Removal must run from outside the worktree.

If GIT_DIR == GIT_COMMON: normal repo, nothing to clean up.

If WORKTREE_PATH under .worktrees/, worktrees/, or ~/.config/reasonix/worktrees/: we created it — we own cleanup:

bash
git worktree remove "$WORKTREE_PATH"
git worktree prune

Otherwise: harness owns workspace. Do NOT remove it. Workspace-exit tool available? Use it. Else leave in place.

Quick Reference

OptionMergePushKeep WorktreeCleanup Branch
1. Merge locallyyes--yes
2. Create PR-yesyes-
3. Keep as-is--yes-
4. Discard---yes (force)

Red Flags

Never: proceed on failing tests; merge without verifying tests on result; delete work without typed confirmation; force-push without explicit request; remove worktree before merge confirmed; clean up worktrees you didn't create; git worktree remove from inside the worktree.

Always: verify tests before options; detect environment before menu; present exactly 4 options (3 detached HEAD); typed confirmation for Option 4; clean up worktree for Options 1 & 4 only; cd to main repo root before removal; git worktree prune after.

© christopherarter, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/superpowers-finishing-a-development-branch of christopherarter/superpowers-reasonix.

Open the folder on GitHubat commit d202ba4

Compare with similar skills

Superpowers Finishing A Development Branch next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Superpowers Finishing A Development Branch compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Superpowers Finishing A Development Branch this skillchristopherarter/superpowers-reasonix102—~1.3kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Finishing A Development Branchfarm-fe/farm5.6k34 repos~1.8kAutomated safety check: PassMIT
Git Worktree Cleanuplobehub/lobehub83k—~2.8kAutomated safety check: PassCustom licence
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
Ccmanager Configkbwo/ccmanager1.3k—~1.5kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Finishing A Development Branch

    farm-fe/farm

    A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…

    5.6k GitHub starsUsed in 34 repos~1.8k tokens
    DevelopmentAuto-check passed

  • Git Worktree Cleanup

    lobehub/lobehub

    Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.

    83k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Ccmanager Config

    kbwo/ccmanager

    Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global ~/.config/ccmanager/config.json.

    1.3k GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Cap Feature Building Workflow

    CapSoftware/Cap

    Builds a Cap feature in an isolated Git worktree with disposable dev resources, verification, a recorded demo and a neutral pull request, started with /building.

    23k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: warnings

More from christopherarter/superpowers-reasonix

All 11 skills in this repo

  • Superpowers Systematic Debugging

    christopherarter/superpowers-reasonix

    Any bug, failing or flaky test, or surprise behavior?. An agent skill from christopherarter/superpowers-reasonix.

    102 GitHub stars~2k tokensUpdated 1 mo ago
    Auto-check passed

  • Superpowers Test Driven Development

    christopherarter/superpowers-reasonix

    Writing or fixing any code?. An agent skill from christopherarter/superpowers-reasonix.

    102 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed

  • Superpowers Writing Skills

    christopherarter/superpowers-reasonix

    Creating, editing, or testing a Reasonix skill?. An agent skill from christopherarter/superpowers-reasonix.

    102 GitHub stars~2.8k tokensUpdated 1 mo ago
    Auto-check passed

  • Superpowers Brainstorming

    christopherarter/superpowers-reasonix

    Building a feature or starting from an idea?. An agent skill from christopherarter/superpowers-reasonix.

    102 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check passed

  • Superpowers Receiving Code Review

    christopherarter/superpowers-reasonix

    Got review feedback?. An agent skill from christopherarter/superpowers-reasonix.

    102 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

  • Superpowers Using Git Worktrees

    christopherarter/superpowers-reasonix

    Feature work needing an isolated workspace, or executing a plan?

    102 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Superpowers Finishing A Development Branch

What does Superpowers Finishing A Development Branch do?

Branch finished, tests green?. An agent skill from christopherarter/superpowers-reasonix. Superpowers Finishing A Development Branch is an agent skill from christopherarter/superpowers-reasonix. Branch finished, tests green?

When should I use Superpowers Finishing A Development Branch?

Superpowers Finishing A Development Branch fits situations like: tasks that involve Git worktrees.

How do I install Superpowers Finishing A Development Branch in Claude Code?

Run `npx skills add christopherarter/superpowers-reasonix --skill superpowers-finishing-a-development-branch -a claude-code`. Or copy the skill folder (skills/superpowers-finishing-a-development-branch in christopherarter/superpowers-reasonix) into .claude/skills/superpowers-finishing-a-development-branch in your project. Claude Code loads it when a task matches its description.

How do I install Superpowers Finishing A Development Branch in Codex?

Run `npx skills add christopherarter/superpowers-reasonix --skill superpowers-finishing-a-development-branch -a codex`. Or copy the skill folder (skills/superpowers-finishing-a-development-branch in christopherarter/superpowers-reasonix) into .agents/skills/superpowers-finishing-a-development-branch in your project. Codex loads it when a task matches its description.

Can I use Superpowers Finishing A Development Branch in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add christopherarter/superpowers-reasonix --skill superpowers-finishing-a-development-branch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/superpowers-finishing-a-development-branch, .gemini/skills/superpowers-finishing-a-development-branch, .github/skills/superpowers-finishing-a-development-branch and .opencode/skills/superpowers-finishing-a-development-branch in your project.

What does Superpowers Finishing A Development Branch need to run?

Going by SKILL.md and its folder, Superpowers Finishing A Development Branch needs the command-line tools its instructions call (git, npm and gh).

Does Superpowers Finishing A Development Branch access the network?

SKILL.md contains no URLs. Its commands use git, npm and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Superpowers Finishing A Development Branch safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Superpowers Finishing A Development Branch use?

Superpowers Finishing A Development Branch is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Superpowers Finishing A Development Branch use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Superpowers Finishing A Development Branch?

Skills that share tags, products or a category with Superpowers Finishing A Development Branch: Finishing a Development Branch (obra/superpowers, 297k stars), Finishing A Development Branch (farm-fe/farm, 5.6k stars), Git Worktree Cleanup (lobehub/lobehub, 83k stars) and Pre-Release PR Triage (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Superpowers Finishing A Development Branch?

christopherarter (a GitHub user) maintains it in christopherarter/superpowers-reasonix, which has 102 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on August 20, 2026.

Source: christopherarter/superpowers-reasonix on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.