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
## Process
1. Verify all tests pass (STOP if they fail)
2. Determine base branch
3. Present exactly 4 options
4. Execute chosen option
5. Clean up worktree (Options 1 and 4 only)
## Agents Used
- Process agents referenced in workflow processes
## Tool Use
Referenced by `executing-plans` and `subagent-driven-development` processes.
The line at the top of this page pins the label git:20260601.da7723a, 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.
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 (863 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
a5c-ai/babysitter · 1,891 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_linsxcovkjgbhneb
GET https://markdownregistry.com/api/v1/resolve?ref=a5c-ai/babysitter/finishing-a-development-branch
GET https://markdownregistry.com/api/v1/blob/d8cdea21f5dfaf99a298b3b47dda158ac555fea6aab2d73a6ef73eaaac200135
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.
a5c-ai/babysitter · .claude/skills/assimilate-popular-workflows/SKILL.md · This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover…
a5c-ai/babysitter · .claude/skills/babysit-babysitter-issues/SKILL.md · This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues"…
a5c-ai/babysitter · .claude/skills/catalog-babysitter-users/SKILL.md · Discover public GitHub repositories that import defineTask from @a5c-ai/babysitter-sdk and maintain a deduplicated…
a5c-ai/babysitter · .claude/skills/fix-failing-pipelines/SKILL.md · This skill should be used when the user asks to "fix pipelines", "fix CI", "check staging pipelines", "fix failing…
a5c-ai/babysitter · .claude/skills/process-builder/SKILL.md · Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the…
a5c-ai/babysitter · .claude/skills/retrospect-external-babysitter-run/SKILL.md · For a repository in the babysitter-users catalog, locate its babysitter processes and any committed runs…
a5c-ai/babysitter · .codex/skills/babysit/SKILL.md · Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called…
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
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…
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…
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…
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.
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…
ed3dai/ed3d-plugins · plugins/ed3d-plan-and-execute/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…
