from-branch SKILL.md skillB
from-branch 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/from-branch@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/from-branch/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261014.0f16275, committed Oct 14, 2026
- First version recorded
- Sep 21, 2026
- Size
- 16,532 bytes
- Repository stars
- 22
- License
- MIT
Attach the current session to an existing branch or PR and continue work from there, abandoning the auto-created session branch. Invoke as `/from-branch <branch-name|#PR|PR-url> [<follow-up instruction or skill ...>]`, a skill in the follow-up named bare (`/from-branch #123 finalize`). The PR target may be a bare PR link or any deep link into it (a review link like `.../pull/NNN#pullrequestreview-<id>`, a review-comment or conversation-comment link, or a `/files` tab URL) — the PR number after…
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
When a Claude Code on-the-web session starts, the harness usually creates a fresh branch (e.g. `claude/add-foo-bar-XXXX`) and checks it out. This skill **discards that auto-branch** and re-points the working tree at an existing branch or PR head so the rest of the session continues that work. ## Recognizing the signal (explicit _and_ implicit) The obvious trigger is an explicit `/from-branch …` invocation. But a session can also **start** with a launch prompt that just names an existing branch to continue — with no literal `/from-branch`. Common shapes: - `go claude/some-feature-xxxx` (or `implement …` / `execute …`), - "continue the work on `<branch>`", "pick up `<branch>`", "keep going on `#123`". These are the **same signal**: the harness has put you on a fresh auto-branch, but the operator's intent is to attach to the _named_ existing branch and continue its work — not to start new work on the auto-branch. Treat such a launch prompt as an implicit `/from-branch <that-branch> <the rest of the prompt as follow-up>` and run this skill: resolve the named branch as the **Target** (Step 1), and take everything …
Read the whole file at its exact version.
How to install
mdr add vzakharov/muthur/from-branch@sha256:98f02fb2e550d1d1The 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_v6zofgkapgyv5fhr)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 21, 2026 and Oct 14, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.0f16275 latest | 2026-10-14 | 0f16275 | 16,532 B | B | view · diff |
| git:20261004.b38d61b | 2026-10-04 | b38d61b | 16,326 B | B | view · diff |
| git:20260930.b7805f2 | 2026-09-30 | b7805f2 | 15,785 B | B | view · diff |
| git:20260930.5675523 | 2026-09-30 | 5675523 | 15,784 B | B | view · diff |
| git:20260921.b2de371 | 2026-09-21 | b2de371 | 15,531 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 (16532 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_v6zofgkapgyv5fhr GET https://markdownregistry.com/api/v1/resolve?ref=vzakharov/muthur/from-branch GET https://markdownregistry.com/api/v1/blob/98f02fb2e550d1d19dcec9967848c6f34df9a00e81131dfbacca245bdf51b342
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.