finishing-a-development-branch SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 6 indexed copies. Same content hash, so the same checks give both the same grade.
finishing-a-development-branch from naimkatiman/continuous-improvement is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add naimkatiman/continuous-improvement/finishing-a-development-branch@git:20260906.6d2507bPins git:20260906.6d2507b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- naimkatiman/continuous-improvement
- Path
third-party/superpowers/skills/finishing-a-development-branch/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260906.6d2507b, committed Sep 6, 2026
- First version recorded
- May 6, 2026
- Size
- 7,781 bytes
- Repository stars
- 9
- License
- MIT
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 → Detect environment → Present options → Execute choice → Clean up. **Announce at start:** "I'm using the finishing-a-development-branch skill to complete this work." ## 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: Detect Environment ```bash 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) # Capture now, while still inside the workspace — Step 5 changes directory # before cleanup (Step 6) needs this value WORKTREE_PATH=$(git rev-parse --show-toplevel) ``` This determines which menu to show and how cleanup works: | State | Menu | Cleanup | |-------|------|---------| | `GIT_DIR == GIT_COMMON` (normal repo) | Standard 3 options | No worktree to clean up | …
Read the whole file at its exact version.
How to install
mdr add naimkatiman/continuous-improvement/finishing-a-development-branch@sha256:8db5a922b242dd4eThe line at the top of this page pins the label git:20260906.6d2507b, 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_zs6rqg45uor74q2t)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 6, 2026 and Sep 6, 2026, about one every 123 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260906.6d2507b latest | 2026-09-06 | 6d2507b | 7,781 B | A | view · diff |
| git:20260506.e373c52 | 2026-05-06 | e373c52 | 7,061 B | A | view |
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 (7781 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
naimkatiman/continuous-improvement · 9 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zs6rqg45uor74q2t GET https://markdownregistry.com/api/v1/resolve?ref=naimkatiman/continuous-improvement/finishing-a-development-branch GET https://markdownregistry.com/api/v1/blob/8db5a922b242dd4e1bf824cb91c13b3e8d8e8a86d6ceaf7f0774eb9cce909d65
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 naimkatiman/continuous-improvement
Every file in naimkatiman/continuous-improvement