subwave-worktree-dev SKILL.md skillA
subwave-worktree-dev from perminder-klair/subwave is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add perminder-klair/subwave/subwave-worktree-dev@git:20261010.b934c39Pins git:20261010.b934c39 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- perminder-klair/subwave
- Path
.claude/skills/subwave-worktree-dev/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261010.b934c39, committed Oct 10, 2026
- First version recorded
- May 23, 2026
- Size
- 9,497 bytes
- Repository stars
- 1,665
- License
- MIT
Stage a SUB/WAVE git worktree so the dev stack can run from it, then start it. A git worktree only checks out tracked files — the dev stack also needs gitignored files (controller/.env, web/.env.local, docker/.env, web/node_modules, and a state/ directory) that this skill copies or scaffolds from the main working tree. Use this skill whenever the user wants to test branch changes in a worktree, run subwave from a worktree, "prep"/"set up" a worktree for dev mode, or asks to copy env files /…
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
# SUB/WAVE worktree dev setup Get the SUB/WAVE dev stack running from inside a **git worktree** so branch changes can be tested without touching the main checkout. ## Why a worktree needs prep A worktree checks out every **tracked** file, so all source is already there. But the dev stack also depends on **gitignored** files that do not travel with a worktree checkout: | File | Why the stack needs it | |---|---| | `.env` | Root `.env` — the controller's **only** `env_file` in dev compose (`./.env`), and compose's substitution source. `ADMIN_USER` / `ADMIN_PASS` / `SITE_URL`, plus `NAVIDROME_*` and LLM/TTS keys. Compose refuses to start without it. | | `controller/.env` | **Legacy — nothing reads it.** Older checkouts still keep `NAVIDROME_*` and API keys here; the script folds any key it has into the worktree's root `.env` (root wins, `ICECAST_*` skipped). Without that, the station boots with `needsSetup: true` and "could not reach http://navidrome:4533". | …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5fgdgipfrlwif3lr/cbd5ec8a5314b002b81604c6b111dc9a8d3ef6e6479a9d9161995c265362fbc7.json
Then /plugin install subwave-worktree-dev@markdownregistry-5fgdgipfrlwif3lr in Claude Code. It installs git:20261010.b934c39, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add perminder-klair/subwave/subwave-worktree-dev@sha256:cbd5ec8a5314b002The line at the top of this page pins the label git:20261010.b934c39, 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_5fgdgipfrlwif3lr)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in perminder-klair/subwave/subwave-worktree-dev since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of subwave-worktree-dev from somewhere else? Ask it: where did my subwave-worktree-dev come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between May 23, 2026 and Oct 10, 2026, about one every 35 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261010.b934c39 latest | 2026-10-10 | b934c39 | 9,497 B | A | view · diff |
| git:20260525.746b046 | 2026-05-25 | 746b046 | 8,475 B | A | view · diff |
| git:20260525.b59d41e | 2026-05-25 | b59d41e | 7,341 B | A | view · diff |
| git:20260524.0efa8b4 | 2026-05-24 | 0efa8b4 | 6,589 B | A | view · diff |
| git:20260523.8ec2102 | 2026-05-23 | 8ec2102 | 6,637 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/subwave-worktree-dev/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (9497 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
perminder-klair/subwave · 1,665 stars · license MIT · pushed 2026-11-17 · branch develop
API
GET https://markdownregistry.com/api/v1/artifacts/art_5fgdgipfrlwif3lr GET https://markdownregistry.com/api/v1/resolve?ref=perminder-klair/subwave/subwave-worktree-dev GET https://markdownregistry.com/api/v1/blob/cbd5ec8a5314b002b81604c6b111dc9a8d3ef6e6479a9d9161995c265362fbc7
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.