finishing-a-development-branch SKILL.md skillA
finishing-a-development-branch in ibrahim-3d/orchestrator-supaconductor is at git:20260327.87e3ef5 (Mar 27, 2026), graded A.
mdr add ibrahim-3d/orchestrator-supaconductor/finishing-a-development-branch@git:20260327.87e3ef5This copy is 3 versions behind it. See what changed · install this older copy instead
This line moves to the next version by itself within about an hour of that file saving one. A copy already installed stays as it is until you update it.
finishing-a-development-branch from neversight/learn-skills.dev is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- neversight/learn-skills.dev
- Path
data/skills-md/0x2e/superpowers/finishing-a-development-branch/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260315.73b2241, committed Mar 15, 2026
- Size
- 4,250 bytes
- Repository stars
- 223
- License
- none declared
Use 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 merge, PR, or cleanup.
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 → 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:** ```bash # 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. ### Step 2: Determine Base Branch ```bash # 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?" ### Step 3: Present Options 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) …
Read the whole file at its exact version.
How to install
mdr add neversight/learn-skills.dev/finishing-a-development-branch@git:20260315.73b2241Pins git:20260315.73b2241 in mdr.lock, 3 versions behind the newest at the top of this page.
claude plugin marketplace add https://markdownregistry.com/mp/a/art_qpl7qz5y6w5ft3uo/dd2f82c6dc8582b621f9eb57fcb65f557f88eadf872727ac81d0840ae12c504e.json
Then /plugin install finishing-a-development-branch@markdownregistry-qpl7qz5y6w5ft3uo in Claude Code. It installs git:20260315.73b2241, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add neversight/learn-skills.dev/finishing-a-development-branch@sha256:dd2f82c6dc8582b6The older copy line above pins the label git:20260315.73b2241, 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.
[](https://markdownregistry.com/a/art_qpl7qz5y6w5ft3uo)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: get me the newest ibrahim-3d/orchestrator-supaconductor/finishing-a-development-branch, and what changed since dd2f82c? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of finishing-a-development-branch from somewhere else? Ask it: where did my finishing-a-development-branch come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Mar 15, 2026.
Watch this file (sign in, one email per new version)
Copies
Newest: git:20260327.87e3ef5 of finishing-a-development-branch in ibrahim-3d/orchestrator-supaconductor (skills/finishing-a-development-branch/SKILL.md), graded A.
This copy: byte for byte that file's version git:20260217.f6fef93, which it committed on Feb 17, 2026, before this repository did; graded A, 3 versions behind.
See what changed since these bytes · ask your agent
Matched on the exact bytes and the commit dates, nothing else. It does not say who wrote the file or where this repository got it.
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/finishing-a-development-branch/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4250 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
neversight/learn-skills.dev · 223 stars · license none declared · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qpl7qz5y6w5ft3uo GET https://markdownregistry.com/api/v1/resolve?ref=neversight/learn-skills.dev/finishing-a-development-branch GET https://markdownregistry.com/api/v1/blob/dd2f82c6dc8582b621f9eb57fcb65f557f88eadf872727ac81d0840ae12c504e
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from neversight/learn-skills.dev
Every file in neversight/learn-skills.dev