cleanup SKILL.md skillA
cleanup from mikestankavich/claude-ship-workflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mikestankavich/claude-ship-workflow/cleanup@git:20260907.bdb897aPins git:20260907.bdb897a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mikestankavich/claude-ship-workflow
- Path
skills/cleanup/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260907.bdb897a, committed Sep 7, 2026
- First version recorded
- Aug 3, 2026
- Size
- 23,242 bytes
- Repository stars
- 3
- License
- MIT
Clean up after a merged pull request — return to the base branch, remove the worktree, delete the branch, sweep other stale branches and worktrees, and report tracker state. Use after a merge or whenever asked what is left over.
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
# Clean up after a merged pull request **Announce at start:** "Using csw:cleanup to close out <ticket>." Once the merge is confirmed, branch and worktree cleanup happens without asking. Closing a ticket always asks. Those two rules are not symmetric and the asymmetry is deliberate. Confirming the merge is itself the one precondition cleanup checks before it removes anything — that check is not optional, even though most of the time it passes instantly. ## Step 1: Confirm the merge, then note where you are Before anything is removed, establish that the PR for this branch is actually merged: ```bash gh pr view --json state,mergedAt ``` If this run was chained straight from **csw:merge**, the merge is already confirmed there — say so, and this check simply passes; the chained path stays frictionless. The only thing that authorises deletion is `gh pr view` reporting `state: MERGED`. Anything else is a stop-and-ask: a non-merged state, no PR for this branch, or **the command failing for any reason** — no auth, no configured remote, a network error, or anything else. Command failure is not "no signal, treat it as merged" — it is exactly the same …
Read the whole file at its exact version.
How to install
mdr add mikestankavich/claude-ship-workflow/cleanup@sha256:036ae6c4a28c6482The line at the top of this page pins the label git:20260907.bdb897a, 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_thzwzb665mzkiekd)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 3, 2026 and Sep 7, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260907.bdb897a latest | 2026-09-07 | bdb897a | 23,242 B | A | view · diff |
| git:20260907.b1a8d57 | 2026-09-07 | b1a8d57 | 22,101 B | A | view · diff |
| git:20260907.02b0667 | 2026-09-07 | 02b0667 | 18,248 B | A | view · diff |
| git:20260803.9ec7b61 | 2026-08-03 | 9ec7b61 | 16,801 B | A | view · diff |
| git:20260803.bc94bb6 | 2026-08-03 | bc94bb6 | 15,207 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 (23242 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
mikestankavich/claude-ship-workflow · 3 stars · license MIT · pushed 2026-09-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_thzwzb665mzkiekd GET https://markdownregistry.com/api/v1/resolve?ref=mikestankavich/claude-ship-workflow/cleanup GET https://markdownregistry.com/api/v1/blob/036ae6c4a28c6482c42add53e2ef663febbb2175194544a60420b41cb2d0067f
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 mikestankavich/claude-ship-workflow
Every file in mikestankavich/claude-ship-workflow