workflow-cleanup-merged SKILL.md skillA
workflow-cleanup-merged from lugassawan/swe-workbench is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lugassawan/swe-workbench/workflow-cleanup-merged@git:20261019.401c6bbPins git:20261019.401c6bb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lugassawan/swe-workbench
- Path
skills/workflow-cleanup-merged/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261019.401c6bb, committed Oct 19, 2026
- First version recorded
- Aug 23, 2026
- Size
- 29,314 bytes
- Repository stars
- 3
- License
- MIT
Use after a PR has been merged on GitHub to remove the local worktree, delete the local branch, delete the remote branch, and fast-forward local main — safely, with squash-merge support.
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
# Workflow: Cleanup Merged Branch **Announce at start:** "I'm using the workflow-cleanup-merged skill to clean up after the merged PR." ## When to Invoke - After the user has confirmed a PR is merged on GitHub. - Invoked by `/swe-workbench:cleanup-merged` (user-triggered, one-off cleanup). - Invoked by Mode C orchestration (`orchestration.md`) at Step 7, after each merge round. **Never auto-trigger.** Cleanup is user-initiated or orchestrator-initiated. Do not attach to a Stop hook. ## What This Skill Does NOT Do - Does not merge PRs — that is the user's action. - Does not force-delete branches with uncommitted work — no `--force`, ever. - Does not squash, rebase, or alter commit history. - Does not bypass branch protection rules. - Does not verify CI status — CI verification happens in Phase 3/4 before the PR is created. ## Cleanup Contract ### Step 1 — Resolve Target PR - If the user passed a PR number → use it directly. - Else → derive from current branch: ``` gh pr view --json number,state,mergedAt,headRefName,headRepository,body ``` Extract `headRefName` as the branch name to clean up. ### Step 2 — Verify Merged via `gh` (Sole Oracle) ``` …
Read the whole file at its exact version.
How to install
mdr add lugassawan/swe-workbench/workflow-cleanup-merged@sha256:842089b362e50ec8The line at the top of this page pins the label git:20261019.401c6bb, 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_lmco3lvvwjf7vi4e)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Aug 23, 2026 and Oct 19, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.401c6bb latest | 2026-10-19 | 401c6bb | 29,314 B | A | view · diff |
| git:20261011.c5cab93 | 2026-10-11 | c5cab93 | 29,275 B | A | view · diff |
| git:20260924.4b76b48 | 2026-09-24 | 4b76b48 | 27,935 B | A | view · diff |
| git:20260905.7b99383 | 2026-09-05 | 7b99383 | 27,559 B | A | view · diff |
| git:20260825.f99a559 | 2026-08-25 | f99a559 | 26,564 B | A | view · diff |
| git:20260824.7e71485 | 2026-08-24 | 7e71485 | 25,313 B | A | view · diff |
| git:20260823.04f991f | 2026-08-23 | 04f991f | 23,961 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 (29314 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
lugassawan/swe-workbench · 3 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lmco3lvvwjf7vi4e GET https://markdownregistry.com/api/v1/resolve?ref=lugassawan/swe-workbench/workflow-cleanup-merged GET https://markdownregistry.com/api/v1/blob/842089b362e50ec8e5e98b3836d42e755a4c7b6d14fdbc8e50c08e95ae1d042c
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.