finishing-a-development-branch skillA
finishing-a-development-branch is agent-read markdown (skill) from yeaight7/agent-powerups: 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.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns 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@git:20260606.0a780d6mdr add yeaight7/agent-powerups/finishing-a-development-branch@sha256:0ed65a6126664c7aPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_7sihdboaw3wfc62m)
0 badge views in 30 days
Versions
| 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 · 6 stars · license Apache-2.0 · pushed 2026-09-21 · 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 agent 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.
More from yeaight7/agent-powerups
Every file in yeaight7/agent-powerups