pitroom-worktrees SKILL.md skillA
pitroom-worktrees from atastech/pitroom is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add atastech/pitroom/pitroom-worktrees@git:20260930.b3d668bPins git:20260930.b3d668b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- atastech/pitroom
- Path
skills/pitroom-worktrees/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260930.b3d668b, committed Sep 30, 2026
- Size
- 7,224 bytes
- Repository stars
- 28
- License
- MIT
Use when starting feature work that needs isolation from the current workspace, or before executing an implementation plan - sets up an isolated branch for your own work (workers get isolated copies from Pitroom itself).
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
# Using Git Worktrees ## Overview Ensure work happens in an isolated workspace. Prefer your platform's native worktree tools. Fall back to manual git worktrees only when no native tool is available. **Core principle:** Detect existing isolation first. Then use native tools. Then fall back to git. Never fight the harness. **Announce at start:** "I'm using the pitroom-worktrees skill to set up an isolated workspace." ## Workers don't need this This skill isolates **your** branch. Pitroom workers never edit your checkout when started with `-i`: each gets a private copy of your current state, and you apply its patch. Don't create a worktree per worker. ## Step 0: Detect Existing Isolation **Before creating anything, check if you are already in an isolated workspace.** ```bash GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P) GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P) BRANCH=$(git branch --show-current) ``` **Submodule guard:** `GIT_DIR != GIT_COMMON` is also true inside git submodules. Before concluding "already in a worktree," verify you are not in a submodule: ```bash …
Read the whole file at its exact version.
How to install
mdr add atastech/pitroom/pitroom-worktrees@sha256:5d6ced1abddb519dThe line at the top of this page pins the label git:20260930.b3d668b, 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_pce3r563nstwjfmg)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 30, 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 (7224 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
atastech/pitroom · 28 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pce3r563nstwjfmg GET https://markdownregistry.com/api/v1/resolve?ref=atastech/pitroom/pitroom-worktrees GET https://markdownregistry.com/api/v1/blob/5d6ced1abddb519d50ba32f2cc57a69ecdd158c86806319187e89cb57132de7c
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.