finishing-a-development-branch SKILL.md skillA
finishing-a-development-branch from coco-research/coco is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add coco-research/coco/finishing-a-development-branch@git:20260914.e75f220Pins git:20260914.e75f220 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- coco-research/coco
- Path
skills/finishing-a-development-branch/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260914.e75f220, committed Sep 14, 2026
- First version recorded
- Apr 26, 2026
- Size
- 4,463 bytes
- Repository stars
- 796
- License
- a license file GitHub does not identify
Use when implementation is done and tests pass and the user must choose to merge locally, open a PR, keep the branch, or discard it. Presents those four options, executes the choice, and cleans up the worktree for merge and discard.
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 ``` If that prints nothing (neither branch exists), ask the user which base branch to use and wait for the answer. Do not continue with `<base-branch>` unset. ### Step 3: Present Options Present exactly these 4 options: ``` Implementation complete. What would you like to do? 1. Merge back to <base-branch> locally …
Read the whole file at its exact version.
How to install
mdr add coco-research/coco/finishing-a-development-branch@sha256:e505b0bf7526dae8The line at the top of this page pins the label git:20260914.e75f220, 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_2idlckoyfml4of6h)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Apr 26, 2026 and Sep 14, 2026, about one every 71 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260914.e75f220 latest | 2026-09-14 | e75f220 | 4,463 B | A | view · diff |
| git:20260802.1479e32 | 2026-08-02 | 1479e32 | 4,270 B | A | view · diff |
| git:20260426.d53cc6c | 2026-04-26 | d53cc6c | 4,250 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 (4463 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
coco-research/coco · 796 stars · license a license file GitHub does not identify · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2idlckoyfml4of6h GET https://markdownregistry.com/api/v1/resolve?ref=coco-research/coco/finishing-a-development-branch GET https://markdownregistry.com/api/v1/blob/e505b0bf7526dae80143ebfdcf8f40df0f014f0042c39d218ffbb489902fe733
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 coco-research/coco
Every file in coco-research/coco