Use when implementation is complete and all tests pass. Decides how to integrate the work via merge, PR, or cleanup with structured options.
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
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."
## The Process
### Step 1: Verify Tests
**Before presenting options, verify tests pass:**
<!-- gate:example-only -->
```bash
# Run project's test suite
npm test / cargo test / pytest / go test ./...
```
<!-- /gate:example-only -->
**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.
### Step 2: Detect Environment
**Determine workspace state before presenting options:**
```bash
# nosec-extract
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 |
|-------|------|---------|
…
The line at the top of this page pins the label git:20261004.8dfccd1, 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_bbngwzgp7pflzk72
GET https://markdownregistry.com/api/v1/resolve?ref=arcanada-one/datarim/finishing-a-development-branch
GET https://markdownregistry.com/api/v1/blob/b0644357b68539ac786e474a37cb38ce28fd3d10087cbf9d8b785cc3bdc85e22
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.
arcanada-one/datarim · plugins/product-discovery/skills/decision-record/SKILL.md · Record bounded product decisions with counterevidence, uncertainty, and explicit reversal conditions.
arcanada-one/datarim · plugins/product-discovery/skills/hypothesis-validation/SKILL.md · Use when a product decision depends on an uncertain claim and needs a bounded, falsifiable check.
arcanada-one/datarim · skills/adversarial-review/SKILL.md · Forces an adversarial mindset on a plan, PRD, design, or code change — break it rather than bless it. Loaded at the…
arcanada-one/datarim · skills/brainstorming/SKILL.md · MUST use this before any creative work — features, components, functionality, behavior changes. Explores user intent…
arcanada-one/datarim · skills/consilium/SKILL.md · Assemble a panel of Datarim agents for multi-perspective analysis of decisions. Use for /dr-design stage (L3-4) or…
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…
