worktree-enhanced SKILL.md skillA
worktree-enhanced from jerseycheese/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jerseycheese/agent-skills/worktree-enhanced@git:20261016.04e815bPins git:20261016.04e815b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jerseycheese/agent-skills
- Path
skills/worktree-enhanced/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261016.04e815b, committed Oct 16, 2026
- First version recorded
- Jun 28, 2026
- Size
- 9,010 bytes
- Repository stars
- 3
- License
- MIT
Sets up a git worktree for isolated feature work: creates the branch, configures the worktree, detects a running dev server, and handles project setup. Trigger on: "create a worktree", "start work on issue #X", "start a feature branch", "work on this in isolation".
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
# Enhanced Worktree Workflow
## When to Use This Skill
Use this skill when:
- Starting work on a new feature or bug fix
- Need isolation from current workspace
- Want parallel development on multiple issues
- Executing implementation plans that require clean state
This skill handles the full worktree setup workflow with:
- Dev server detection and coordination
- Local env file propagation from the main checkout
- Automatic dev server startup option
- Project-specific worktree conventions
## Enhanced Features
### 1. Dev Server Awareness
Every worktree gets its own dev-server port — never assume port 3000 belongs to the worktree you're in. If the project has adopted the per-worktree port pattern (`scripts/worktree-port.cjs`, installed by `install-worktree-port.sh`), resolve the port before checking it:
```bash
# Resolve this checkout's port: the per-worktree script if the project has it
# installed, else the port recorded in .claude/launch.json, else 3000 (the
# main-checkout default)
if [ -f scripts/worktree-port.cjs ]; then
PORT="$(node scripts/worktree-port.cjs)"
else
PORT="$(node -p "require('./.claude/launch.json').configurations[0].port" 2>/dev/null || echo 3000)"
…Read the whole file at its exact version.
How to install
mdr add jerseycheese/agent-skills/worktree-enhanced@sha256:0c83dd9c0faf2b90The line at the top of this page pins the label git:20261016.04e815b, 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_anzpgn6lrrcri5d5)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jun 28, 2026 and Oct 16, 2026, about one every 37 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.04e815b latest | 2026-10-16 | 04e815b | 9,010 B | A | view · diff |
| git:20260725.5df3f26 | 2026-07-25 | 5df3f26 | 9,145 B | A | view · diff |
| git:20260725.4a22f66 | 2026-07-25 | 4a22f66 | 6,612 B | A | view · diff |
| git:20260628.9366aee | 2026-06-28 | 9366aee | 6,616 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 (9010 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
jerseycheese/agent-skills · 3 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_anzpgn6lrrcri5d5 GET https://markdownregistry.com/api/v1/resolve?ref=jerseycheese/agent-skills/worktree-enhanced GET https://markdownregistry.com/api/v1/blob/0c83dd9c0faf2b90464cd16340691cd7a79732925c6885837c30099076c1c877
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.