finishing-a-development-branch SKILL.md skillA
finishing-a-development-branch from yeaight7/agent-powerups is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yeaight7/agent-powerups/finishing-a-development-branch@git:20260606.0a780d6Pins git:20260606.0a780d6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yeaight7/agent-powerups
- Path
skills/finishing-a-development-branch/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260606.0a780d6, committed Jun 6, 2026
- First version recorded
- Apr 30, 2026
- Size
- 3,284 bytes
- Repository stars
- 8
- License
- Apache-2.0
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. ## The Process ### Step 1: Verify Tests **Before presenting options, verify tests pass:** ```bash npm test / cargo test / pytest / go test ./... ``` **If tests fail:** Show failures. Stop. Don't proceed to Step 2. **If tests pass:** Continue to Step 2. ### Step 2: Determine Base Branch ```bash git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null ``` ### 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) 4. Discard this work Which option? ``` **Don't add explanation** — keep options concise. ### Step 4: Execute Choice #### Option 1: Merge Locally ```bash git checkout <base-branch> git pull git merge <feature-branch> <test command> # verify tests on merged result git branch -d <feature-branch> ``` #### Option 2: Push and Create PR …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/finishing-a-development-branch@sha256:0ed65a6126664c7aThe line at the top of this page pins the label git:20260606.0a780d6, 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_7sihdboaw3wfc62m)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Apr 30, 2026 and Jun 6, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.0a780d6 latest | 2026-06-06 | 0a780d6 | 3,284 B | A | view · diff |
| git:20260430.f10c0a1 | 2026-04-30 | f10c0a1 | 2,874 B | A | view · diff |
| git:20260430.344cada | 2026-04-30 | 344cada | 2,942 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 (3284 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
yeaight7/agent-powerups · 8 stars · license Apache-2.0 · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7sihdboaw3wfc62m GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/finishing-a-development-branch GET https://markdownregistry.com/api/v1/blob/0ed65a6126664c7ab450d2655be05b261427215817a3653ce6b907cfd3bc6c1b
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 yeaight7/agent-powerups
Every file in yeaight7/agent-powerups