merged-branch-cleanup Cursor ruleA
merged-branch-cleanup from coddy-project/coddy-agent is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add coddy-project/coddy-agent/.cursor/rules/merged-branch-cleanup.mdc@git:20261013.2836adePins git:20261013.2836ade in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- coddy-project/coddy-agent
- Path
.cursor/rules/merged-branch-cleanup.mdc- Versions recorded
- 1
- Latest version
- git:20261013.2836ade, committed Oct 13, 2026
- Size
- 3,710 bytes
- Repository stars
- 178
- License
- MIT
After a pull request merges, remove its worktree and delete its branch, locally and on origin.
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
# Cleanup after a merge A branch whose pull request has merged is finished, and its worktree and the branch itself are removed in the same session, as the last step of the merge rather than later. A worktree left behind keeps a checkout, a `node_modules` and a build cache on the disk; a branch left behind is where the next agent commits a follow-up that no pull request will ever pick up. ## When it applies As soon as you know that the pull request of a branch you worked on has merged: you merged it (*Merging the pull request* in the **workflow rule**), the operator says so, or `gh pr view <PR> --json state` reports `MERGED`. It covers a worktree a host made for the session (`.claude/worktrees/`, `.coddy/worktrees/` and the like) as much as one made by hand, and the isolated site-repository worktree once its commit is pushed. A branch that reached `main` by a direct push, with no pull request, is finished the same way once the push is confirmed. Step 1 then checks it against `main` instead of a pull request (`git -C <main checkout> fetch origin`, then `git -C <main checkout> merge-base --is-ancestor <branch> origin/main`), and step 4 has nothing to …
Read the whole file at its exact version.
How to install
mdr add coddy-project/coddy-agent/.cursor/rules/merged-branch-cleanup.mdc@sha256:09d6a9fd524121e0The line at the top of this page pins the label git:20261013.2836ade, 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_rcimmi4dkyvi7j6s)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 13, 2026.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (3710 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
coddy-project/coddy-agent · 178 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rcimmi4dkyvi7j6s GET https://markdownregistry.com/api/v1/resolve?ref=coddy-project/coddy-agent/.cursor/rules/merged-branch-cleanup.mdc GET https://markdownregistry.com/api/v1/blob/09d6a9fd524121e0e01c0139bd7c8f02329bf7295c51d188c4fcb2f0853cc091
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: Cursor rules vs AGENTS.md · which agent file does what.