Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Finishing a Development Branch
## Overview
**Core principle:** Verify tests → Verify UML model alignment → Detect environment → Present options → Execute choice → Clean up.
**Announce at start:** "I'm using the finishing-a-development-branch skill to complete this work."
## The Iron Law
```
NO UML MODEL ELEMENTS OR DIAGRAMS THAT DO NOT MATCH THE CODE
```
If the UML model element or diagram is inconsistent with the code, it must be brought into alignment with the code.
## Step 1: Verify Tests
Run the project's full test suite (`npm test` / `cargo test` / `pytest` / `go test ./...`).
**If tests fail**, report the failures and stop — the menu comes after a green suite:
```
Tests failing (<N> failures). Must fix before completing:
[Show failures]
```
**If tests pass:** continue to Step 2.
## Step 2: Verify UML Model Alignment
**First, confirm Astah has this branch's model open.** Call `get_proj_path` and
compare it against this working tree:
```bash
git rev-parse --show-toplevel
```
| `get_proj_path` returns | Action |
|---|---|
| A path under this working tree | Proceed with verification |
…
The line at the top of this page pins the label git:20260815.6743039, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_36ucmn6otdzij5hb
GET https://markdownregistry.com/api/v1/resolve?ref=takaakit/superpowers-uml/finishing-a-development-branch
GET https://markdownregistry.com/api/v1/blob/7137145109c25af57d6a80b57de06a8d1bec6fb0e754ef5dcf85cb4261add3cc
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
takaakit/superpowers-uml · plugins/superpowers-uml/skills/brainstorming/SKILL.md · You MUST use this before any creative work - creating features, building components, adding functionality, or modifying…
takaakit/superpowers-uml · plugins/superpowers-uml/skills/dispatching-parallel-agents/SKILL.md · Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
takaakit/superpowers-uml · plugins/superpowers-uml/skills/executing-plans/SKILL.md · Use when you have a written implementation plan to execute in a separate session with review checkpoints
takaakit/superpowers-uml · plugins/superpowers-uml/skills/receiving-code-review/SKILL.md · Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or…
takaakit/superpowers-uml · plugins/superpowers-uml/skills/requesting-code-review/SKILL.md · Use when completing tasks, implementing major features, or before merging to verify work meets requirements
takaakit/superpowers-uml · plugins/superpowers-uml/skills/subagent-driven-development/SKILL.md · Use when executing implementation plans with independent tasks in the current session
takaakit/superpowers-uml · plugins/superpowers-uml/skills/systematic-debugging/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
takaakit/superpowers-uml · plugins/superpowers-uml/skills/test-driven-development/SKILL.md · Use when implementing any feature or bugfix, before writing implementation code
takaakit/superpowers-uml · plugins/superpowers-uml/skills/using-git-worktrees/SKILL.md · Use when starting feature work that needs isolation from current workspace or before executing implementation plans -…
takaakit/superpowers-uml · plugins/superpowers-uml/skills/using-superpowers/SKILL.md · Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY…
takaakit/superpowers-uml · plugins/superpowers-uml/skills/verification-before-completion/SKILL.md · Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running…
takaakit/superpowers-uml · plugins/superpowers-uml/skills/writing-plans/SKILL.md · Use when you have a spec or requirements for a multi-step task, before touching code
obra/superpowers · skills/finishing-a-development-branch/SKILL.md · Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
a5c-ai/babysitter · library/methodologies/superpowers/skills/finishing-a-development-branch/SKILL.md · Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
ganyuanran/aegis · skills/finishing-a-development-branch/SKILL.md · Use when verified work needs integration or cleanup of an existing task-created branch/worktree, or the user explicitly…
coco-research/coco · skills/finishing-a-development-branch/SKILL.md · Use when implementation is done and tests pass and the user must choose to merge locally, open a PR, keep the branch…
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/finishing-a-development-branch/SKILL.md · Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides…
jamditis/claude-skills-journalism · superjawn/skills/finishing-a-development-branch/SKILL.md · Presents options for merge, PR, or cleanup. Use when work is complete, tests pass, and you must decide how to integrate.
ibrahim-3d/orchestrator-supaconductor · skills/finishing-a-development-branch/SKILL.md · Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides…