finishing-a-development-branch SKILL.md skillA

The newest version of a file that held these bytes earlier

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.87e3ef5

This 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

This older copy, pinned
mdr add neversight/learn-skills.dev/finishing-a-development-branch@git:20260315.73b2241

Pins git:20260315.73b2241 in mdr.lock, 3 versions behind the newest at the top of this page.

No tool to install first
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.

The exact contents, by fingerprint
mdr add neversight/learn-skills.dev/finishing-a-development-branch@sha256:dd2f82c6dc8582b6

The 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_qpl7qz5y6w5ft3uo.svg)](https://markdownregistry.com/a/art_qpl7qz5y6w5ft3uo)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
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)

versioncommittedcommitsizeaudit
git:20260315.73b2241 latest2026-03-15 73b2241 4,250 BA view

Copies

The newest version, then this copy

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.

Keep it current by itself, install once

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.

Install on GitHub

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.

Keep it current by itself

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.

Check a whole project

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

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • 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

GitHub

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

knowledge-base-gap-finder SKILL.md skill
neversight/learn-skills.dev · data/skills-md/00prabalk00/claude-skills/knowledge-base-gap-finder/SKILL.md · Identify what documentation is missing by comparing support issues, product behavior, and existing docs. Use when the…
git:20260323.e34c23b · audit A · 223 stars
jira-agile SKILL.md skill
neversight/learn-skills.dev · data/skills-md/01000001-01001110/agent-jira-skills/jira-agile/SKILL.md · Manage Jira Agile boards and sprints. Use when listing boards, creating sprints, or moving issues to/from sprints.
git:20260222.f61e827 · audit A · 223 stars
jira-auth SKILL.md skill
neversight/learn-skills.dev · data/skills-md/01000001-01001110/agent-jira-skills/jira-auth/SKILL.md · Authenticate with Jira Cloud REST API using API tokens. Use when setting up Jira connections, validating credentials…
git:20260222.f61e827 · audit A · 223 stars
jira-issues SKILL.md skill
neversight/learn-skills.dev · data/skills-md/01000001-01001110/agent-jira-skills/jira-issues/SKILL.md · Create, read, update, and delete Jira issues. Use when managing Stories, Tasks, Bugs, or Epics - includes field updates…
git:20260222.f61e827 · audit A · 223 stars
jira-project-management SKILL.md skill
neversight/learn-skills.dev · data/skills-md/01000001-01001110/agent-jira-skills/jira-project-management/SKILL.md · Administer Jira projects. Use when creating/archiving projects, managing components, versions, roles, permissions, or…
git:20260201.679e6b0 · audit A · 223 stars
jira-projects SKILL.md skill
neversight/learn-skills.dev · data/skills-md/01000001-01001110/agent-jira-skills/jira-projects/SKILL.md · Manage Jira projects. Use when listing projects, getting project configuration, retrieving issue types, or managing…
git:20260222.f61e827 · audit A · 223 stars
jira-safe SKILL.md skill
neversight/learn-skills.dev · data/skills-md/01000001-01001110/agent-jira-skills/jira-safe/SKILL.md · Implement SAFe methodology in Jira. Use when creating Epics, Features, Stories with proper hierarchy, acceptance…
git:20260222.f61e827 · audit A · 223 stars
jira-search SKILL.md skill
neversight/learn-skills.dev · data/skills-md/01000001-01001110/agent-jira-skills/jira-search/SKILL.md · Search Jira issues using JQL queries. Use when filtering issues by project, status, assignee, date, or building reports.
git:20260222.f61e827 · audit A · 223 stars
jira-spaces SKILL.md skill
neversight/learn-skills.dev · data/skills-md/01000001-01001110/agent-jira-skills/jira-spaces/SKILL.md · Manage Confluence spaces for project documentation. Create, list, and delete spaces with templates. Use when setting up…
git:20260222.f61e827 · audit A · 223 stars
jira-transitions SKILL.md skill
neversight/learn-skills.dev · data/skills-md/01000001-01001110/agent-jira-skills/jira-transitions/SKILL.md · Move Jira issues through workflow states. Use when transitioning issues (To Do, In Progress, Done) or setting…
git:20260222.f61e827 · audit A · 223 stars
wechat-publisher SKILL.md skill
neversight/learn-skills.dev · data/skills-md/0731coderlee-sudo/wechat-publisher/wechat-publisher/SKILL.md · 一键发布 Markdown 到微信公众号草稿箱。基于 wenyan-cli,支持多主题、代码高亮、图片自动上传。
git:20260206.be9882e · audit A · 223 stars
conventionalcommits SKILL.md skill
neversight/learn-skills.dev · data/skills-md/0froq/skills/conventionalcommits/SKILL.md · Conventional Commits specification for semantic versioning and changelog generation. Use when writing commit messages…
v2026.3.25 · audit A · 223 stars

Every file in neversight/learn-skills.dev

Other files named finishing-a-development-branch

finishing-a-development-branch SKILL.md skill
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
git:20260812.b36e082 · audit A · 319,649 stars
finishing-a-development-branch SKILL.md skill
jnmetacode/superpowers-zh · skills/finishing-a-development-branch/SKILL.md · 当实现完成、所有测试通过、需要决定如何集成这份工作时使用
v1.9.1 · audit A · 8,551 stars
finishing-a-development-branch SKILL.md skill
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.
git:20260601.da7723a · audit A · 1,914 stars
finishing-a-development-branch SKILL.md skill
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…
git:20261010.8d5b88e · audit A · 1,442 stars
finishing-a-development-branch SKILL.md skill
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…
git:20260912.5e131e8 · audit A · 673 stars
finishing-a-development-branch SKILL.md skill
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…
git:20260914.e75f220 · audit A · 631 stars
finishing-a-development-branch SKILL.md skill
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.
git:20261024.21f0bb2 · audit A · 456 stars
finishing-a-development-branch SKILL.md skill
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…
git:20260327.87e3ef5 · audit A · 384 stars

Browse by kind, by grade A, or by owner.