exit-strategy SKILL.md skillA
exit-strategy from kucherenko/gangsta is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kucherenko/gangsta/exit-strategy@git:20260413.7bb5456Pins git:20260413.7bb5456 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kucherenko/gangsta
- Path
skills/exit-strategy/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260413.7bb5456, committed Apr 13, 2026
- First version recorded
- Apr 13, 2026
- Size
- 4,422 bytes
- Repository stars
- 86
- License
- MIT
Use when implementation is complete and all tests pass — guides the clean exit from a development branch with 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
# The Exit Strategy: Finishing a Development Branch ## Overview Every operation needs a clean exit. Guide completion of development work by verifying, presenting options, executing, and cleaning up. **Core principle:** Verify tests → Present options → Execute choice → Clean up. **Announce at start:** "Initiating exit strategy for this branch." ## 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 exiting: [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 ``` Or ask the Don: "This branch split from main — is that correct?" ### Step 3: Present Options Present exactly these 4 options: ``` Implementation complete. What's the exit strategy? 1. Merge back to <base-branch> locally 2. Push and create a Pull Request …
Read the whole file at its exact version.
How to install
mdr add kucherenko/gangsta/exit-strategy@sha256:c54cacc02e216187The line at the top of this page pins the label git:20260413.7bb5456, 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_dch7flmvpin23ufv)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Apr 13, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260413.7bb5456 latest | 2026-04-13 | 7bb5456 | 4,422 B | A | view · diff |
| git:20260413.3b3c977 | 2026-04-13 | 3b3c977 | 4,432 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 (4422 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
kucherenko/gangsta · 86 stars · license MIT · pushed 2026-10-27 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_dch7flmvpin23ufv GET https://markdownregistry.com/api/v1/resolve?ref=kucherenko/gangsta/exit-strategy GET https://markdownregistry.com/api/v1/blob/c54cacc02e21618748cc0657a6613cdf98d001344fd0b1ecc7d65972a0eaa6e3
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.