Helps decide merge, PR, or cleanup steps after branch work is complete.
This skill appears to be an open-source prompt-style development workflow guide with no required secrets and no declared remote endpoints, so the overall risk is low. Caution is still warranted because the README includes executable git/test/push/PR instructions that, if followed by the host environment, would involve local code operations and possible network interaction, but this reflects normal developer workflow rather than a concrete red flag.
The material explicitly states that no keys or environment variables are required, and the README does not ask the user to provide extra tokens. It may only indirectly rely on existing host authentication for gh/git push, with no described behavior to collect or exfiltrate credentials.
No standalone remote endpoint is declared, and the skill itself is prompt-only. However, the README includes git pull, git push, and gh pr create steps which, if executed, would connect to the code hosting remote and may upload branch/PR content; this is normal egress within its stated purpose.
The README explicitly provides commands such as npm test/cargo test/pytest/go test, git, and gh, indicating an expectation that the host can run local developer commands and processes. This is a normal capability for a development-assistance skill, with no sign of unrelated privilege requests or covert execution.
Its workflow reads repository state, branch relationships, and test results, and may modify the workspace and git history (merge, delete branch, discard work). The access scope is largely limited to the current project context, with no evidence of broad access beyond the stated purpose, though destructive repository operations are part of the workflow risk.
The source is an open GitHub repository, and the system marks it as open-source and prompt-only, which improves auditability. Although there is no declared license, it has 0 stars, and maintenance is unknown, there is still no evidence of closed-source exfiltration, suspicious install scripts, or obvious injection/deception red flags.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "finishing-a-development-branch" skill from askskill: 1. Download https://raw.githubusercontent.com/obra/superpowers/main/skills/finishing-a-development-branch/SKILL.md 2. Save it as ~/.claude/skills/finishing-a-development-branch/SKILL.md 3. Reload skills and tell me it's ready
I’ve finished work on this feature branch and all relevant tests are passing. Give me a structured recommendation on whether I should merge directly, open a PR, or do cleanup first, and explain when each option applies and what to do next.
A structured wrap-up recommendation comparing merge, PR, and cleanup options with a suggested path.
Create a completion checklist for a development branch that is fully implemented and passing tests. Cover code review readiness, commit cleanup, documentation updates, PR description, pre-merge validation, and branch cleanup.
An actionable completion checklist to standardize the branch integration process.
I’m about to submit this completed development branch as a PR. Help me prepare the PR contents, including a change summary, test results, risks, review focus areas, and post-merge cleanup tasks.
A PR-ready integration note set that supports review and smooth merging.
Guide completion of development work by presenting clear options and handling chosen workflow.
Core principle: Verify tests → Detect environment → Present options → Execute choice → Clean up.
Announce at start: "I'm using the finishing-a-development-branch skill to complete this work."
Before presenting options, verify tests pass:
# Run project's test suite
npm test / cargo test / pytest / go test ./...
If tests fail:
Tests failing (<N> failures). Must fix before completing:
[Show failures]
Cannot proceed with merge/PR until tests pass.
Stop. Don't proceed to Step 2.
If tests pass: Continue to Step 2.
Determine workspace state before presenting options:
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)
This determines which menu to show and how cleanup works:
| State | Menu | Cleanup |
|---|---|---|
GIT_DIR == GIT_COMMON (normal repo) | Standard 4 options | No worktree to clean up |
GIT_DIR != GIT_COMMON, named branch | Standard 4 options | Provenance-based (see Step 6) |
GIT_DIR != GIT_COMMON, detached HEAD | Reduced 3 options (no merge) | No cleanup (externally managed) |
# Try common base branches
git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null
Or ask: "This branch split from main - is that correct?"
Normal repo and 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.
# Get main repo root for CWD safety
MAIN_ROOT=$(git -C "$(git rev-parse --git-common-dir)/.." rev-parse --show-toplevel)
cd "$MAIN_ROOT"
# Merge first — verify success before removing anything
git checkout <base-branch>
git pull
git merge <feature-branch>
# Verify tests on merged result
<test command>
# Only after merge succeeds: cleanup worktree (Step 6), then delete branch
Then: Cleanup worktree (Step 6), then delete branch:
git branch -d <feature-branch>
# Push branch
git push -u origin <feature-branch>
# Create PR
gh pr create --title "<title>" --body "$(cat <<'EOF'
## Summary
<2-3 bullets of what changed>
## Test Plan
- [ ] <verification steps>
EOF
)"
Do NOT clean up worktree — user needs it alive to iterate on PR feedback.
Report: "Keeping branch <name>. Worktree preserved at <path>."
Don't cleanup worktree.
Confirm first:
This will permanently delete:
- Branch <name>
- All commits: <commit-list>
- Worktree at <path>
Type 'discard' to confirm.
Wait for exact confirmation.
If confirmed:
MAIN_ROOT=$(git -C "$(git rev-parse --git-common-dir)/.." rev-parse --show-toplevel)
cd "$MAIN_ROOT"
Then: Cleanup worktree (Step 6), then force-delete branch:
git branch -D <feature-branch>
Only runs for Options 1 and 4. Options 2 and 3 always preserve the worktree.
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)
…
Execute implementation plans by splitting and advancing independent tasks in-session.
Create, revise, and validate AI skills before deployment.
Systematically investigate bugs, test failures, and unexpected behavior before fixing.
Turn requirements into a clear step-by-step execution plan before implementation.
Set conversation rules to discover and invoke skills before replying.
Clarify intent, requirements, and solution direction before any creative implementation work.
Helps developers finish a branch with merge, PR, or cleanup workflows.
Finalize completed work by committing, pushing, and opening reviewed pull requests.
Create, switch, and verify Git branches before starting implementation work.
Suggests the most suitable next implementation task after finishing current work.
Apply the right commit prefix, reviewer, and test plan for code changes.
Coordinate behavior-preserving code refactors with tests, review, and gated commits.