repo-cleanup SKILL.md skillA
repo-cleanup from heapy/kortex is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add heapy/kortex/repo-cleanup@git:20261009.2001e8aPins git:20261009.2001e8a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- heapy/kortex
- Path
plugins/heapy/skills/repo-cleanup/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261009.2001e8a, committed Oct 9, 2026
- Size
- 11,537 bytes
- Repository stars
- 7
- License
- Apache-2.0
Manually invoke repo-cleanup to tidy a local Git repository: remove branches fully merged into main and their clean worktrees, inspect working directories, propose atomic commits, and review Git stash and IntelliJ IDEA shelves. Run only when the user explicitly invokes this skill; never select it automatically during development or after another task.
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
# Repository Cleanup Run only on the user's explicit invocation. Scope the run to the selected repository and its linked worktrees. A normal invocation authorizes the eligible local branch and worktree removals below; announce the concrete candidates and proceed without another confirmation. `audit`, `dry-run`, or `report only` means inspection and proposals only, with no fetch or other mutations. Creating commits, applying or deleting stash/shelf entries, deleting remote branches or tags, and discarding files require separate explicit instructions. Propose atomic commits by default. Never turn a request to create or edit this skill into a cleanup run. ## Establish scope and baseline 1. Resolve the repository root, common Git directory, current worktree and branch. Read repository guidance and any branch retention rules. Record the initial status, branch tips and worktree paths so the final report can distinguish existing work from cleanup actions. 2. Use `refs/heads/main` as the integration target unless the user specifies another branch. If it is absent, resolve the intended target from repository guidance or ask; do not silently use `HEAD`. …
Read the whole file at its exact version.
How to install
mdr add heapy/kortex/repo-cleanup@sha256:6b624f79f1a52d64The line at the top of this page pins the label git:20261009.2001e8a, 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_umq2jeztkcwhq74b)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 9, 2026.
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 (11537 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
heapy/kortex · 7 stars · license Apache-2.0 · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_umq2jeztkcwhq74b GET https://markdownregistry.com/api/v1/resolve?ref=heapy/kortex/repo-cleanup GET https://markdownregistry.com/api/v1/blob/6b624f79f1a52d649ed61163bcdfe23f4ff930dcdf3eb08543c51c04a0668a43
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.