branch-rename SKILL.md skillB
branch-rename from vzakharov/muthur is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vzakharov/muthur/branch-rename@git:20261014.0f16275Pins git:20261014.0f16275 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vzakharov/muthur
- Path
.claude/skills/branch-rename/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261014.0f16275, committed Oct 14, 2026
- First version recorded
- Aug 8, 2026
- Size
- 4,954 bytes
- Repository stars
- 22
- License
- MIT
Rename the current auto-generated session branch (e.g. `claude/<adjective>-<noun>-<hash>`) to a semantic name derived from the current PR or branch diff. Usually invoked with no args as `/branch-rename`; an optional argument overrides the derived slug, and `force` (`/branch-rename force [<slug>]`) re-slugs a branch that is already semantically named. Use when the user says "rename branch", "rename the branch", or "/branch-rename".
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
Rename the current harness-assigned branch (e.g. `claude/relaxed-brown-EhDOB`) to a semantic name in the form `claude/<short-task-slug>-<hash>` — keep the original random suffix, swap the adjective-noun for a task slug. **Why, and why early.** `claude/lucid-hamilton-MigdG` tells nobody anything in `git log`, PR lists or a later search; `claude/rename-autobranches-MigdG` does, and the kept suffix keeps parallel sessions unique. Rename as soon as the task's scope is clear and **before the first commit**, since `/plan` names the plan file after the branch slug — and always before a PR opens, because renaming a PR's head closes that PR (below). ## First: is the branch already semantic? Inspect `git branch --show-current`. If it's already a meaningful `claude/<slug>-<hash>`, `feat/…`, `fix/…` (etc.) that reflects the task — which the harness now often assigns directly — there's nothing to do: report that and stop. Only proceed with the rename when the name is an opaque `claude/<adjective>-<noun>-<hash>`. (This semantic-autoname behavior is undocumented and may be reverted, which is why the rename procedure stays as the fallback.) …
Read the whole file at its exact version.
How to install
mdr add vzakharov/muthur/branch-rename@sha256:0e4a023b319eade4The line at the top of this page pins the label git:20261014.0f16275, 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_ik4h2ehzxsnvrnsv)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 8, 2026 and Oct 14, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.0f16275 latest | 2026-10-14 | 0f16275 | 4,954 B | B | view · diff |
| git:20261004.b38d61b | 2026-10-04 | b38d61b | 4,926 B | B | view · diff |
| git:20260923.d6730fb | 2026-09-23 | d6730fb | 4,601 B | B | view · diff |
| git:20260811.1f42f0a | 2026-08-11 | 1f42f0a | 4,256 B | B | view · diff |
| git:20260808.a6a6344 | 2026-08-08 | a6a6344 | 4,262 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4954 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
vzakharov/muthur · 22 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ik4h2ehzxsnvrnsv GET https://markdownregistry.com/api/v1/resolve?ref=vzakharov/muthur/branch-rename GET https://markdownregistry.com/api/v1/blob/0e4a023b319eade463044a1d12975c8bd88e0321fcd25cf3e0c46099b86eac5d
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.