Agent skill

Dev Worktree

by codeaholicguy in codeaholicguy/ai-devkit

AI DevKit · Worktree setup and resume guidance for isolated feature work.

Apache-2.0Auto-check passedDevelopment

Install Dev Worktree

skills CLI
$ npx skills add codeaholicguy/ai-devkit --skill dev-worktree -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install codeaholicguy/ai-devkit dev-worktree --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/codeaholicguy/ai-devkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/dev-worktree .claude/skills/dev-worktree && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dev-worktree
GitHub stars
1.6k
Token cost
~980 tokens
SKILL.md length
496 words
Files
2
Skills in repo
28
Repo updated
First seen
Licence
Apache-2.0

At a glance

AI DevKit · Worktree setup and resume guidance for isolated feature work.

  • Works in 6 steps: Propose the exact workspace plan before… → Confirm the target branch/worktree with… → Use feature- for branch and worktree… → …
  • Verifying a feature branch/worktree for lifecycle
  • SKILL.md covers Phase Contract, Start Feature Workspace, Resume Feature Workspace and Dependency Bootstrap, plus 1 more section
  • Calls git, npm and cargo

What it does

Dev Worktree is an agent skill from codeaholicguy/ai-devkit. AI DevKit · Worktree setup and resume guidance for isolated feature work. Use when starting, resuming, switching, or verifying a feature branch/worktree for lifecycle, debugging, implementation, review, or multi-agent workflows.

Its SKILL.md is about 980 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Git worktrees. It works with Git. The repository describes itself as: The control plane for AI coding agents. The licence is Apache-2.0.

When your agent uses it

  • Verifying a feature branch/worktree for lifecycle
  • Multi-agent workflows

Example prompts

  • “/dev-worktree”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Propose the exact workspace plan before changing branch or worktree state.
  2. Confirm the target branch/worktree with the user before switching contexts.
  3. Use feature- for branch and worktree names, where is normalized kebab-case without the prefix.
  4. Prefer a project-local worktree at /.worktrees/feature-.
  5. Use no-worktree mode only when the user explicitly requests it.
  6. Run all follow-up commands in the verified target context.

What it can do on your machine

Read from SKILL.md and the folder at commit 7ef0cd5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • npm
    • cargo
    • pnpm
    • yarn
    • bun
    • uv
    • poetry
    • pip
    • bundle
    • go

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, npm, pnpm, yarn, uv and pip, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dev Worktree loads about 980 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 496 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~980

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from codeaholicguy/ai-devkit at commit 7ef0cd5, republished under its Apache-2.0 licence (© codeaholicguy). 496 words, ~980 tokens.

Download SKILL.mdSave it as .claude/skills/dev-worktree/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
dev-worktree
description
AI DevKit · Worktree setup and resume guidance for isolated feature work. Use when starting, resuming, switching, or verifying a feature branch/worktree for lifecycle, debugging, implementation, review, or multi-agent workflows.

Dev Worktree

Set up or resume the correct workspace before feature work. Keep this skill focused on repository context, worktree isolation, and dependency bootstrap. Do not perform requirements, design, planning, implementation, testing, or review work here.

Phase Contract

  1. Propose the exact workspace plan before changing branch or worktree state.
  2. Confirm the target branch/worktree with the user before switching contexts.
  3. Use feature-<name> for branch and worktree names, where <name> is normalized kebab-case without the prefix.
  4. Prefer a project-local worktree at <project-root>/.worktrees/feature-<name>.
  5. Use no-worktree mode only when the user explicitly requests it.
  6. Run all follow-up commands in the verified target context.

Start Feature Workspace

Use for a new feature start.

  1. Normalize feature name to kebab-case <name>.
  2. Determine the project root, the directory containing .git.
  3. If the user explicitly requests no worktree:
    • Continue in the current repository and branch.
    • Call out that branch/workspace isolation is reduced.
    • Skip to dependency bootstrap.
  4. Otherwise use branch/worktree name feature-<name>.
  5. Ensure .worktrees is listed in the project .gitignore; if not, add it.
  6. If branch does not exist, run git worktree add -b feature-<name> .worktrees/feature-<name>.
  7. If branch exists and the target worktree does not, run git worktree add .worktrees/feature-<name> feature-<name>.
  8. If the target worktree already exists, reuse it after verifying it is clean enough for the requested work.
  9. Verify worktree context with git -C .worktrees/feature-<name> branch --show-current; it must equal feature-<name>.
  10. Return the active workdir path for the next phase.

Resume Feature Workspace

Use when continuing an existing feature.

  1. Check current branch with git branch --show-current.
  2. Check available worktrees with git worktree list.
  3. Prefer <project-root>/.worktrees/feature-<name> when it exists.
  4. Otherwise use branch feature-<name> in the current repository.
  5. Include the selected target in the plan and wait for approval before switching.
  6. After approval, run future phase commands in the selected context.
Show full SKILL.md (184 more words)Show less

Dependency Bootstrap

After selecting the target context:

  1. Detect ecosystem from lockfiles, manifests, and tooling configs.
  2. Prefer deterministic lockfile-based installs.
  3. Use the repository-native command:
    • JavaScript/TypeScript: npm ci, pnpm install --frozen-lockfile, yarn install --frozen-lockfile, or bun install --frozen-lockfile.
    • Python: uv sync, poetry install --no-interaction, pipenv sync, or pip install -r requirements.txt.
    • Ruby: bundle install.
    • Rust: cargo fetch, or cargo build when fetch-only is insufficient.
    • Go: go mod download.
    • Java/Kotlin: ./gradlew dependencies, ./gradlew build, or Maven equivalent.
  4. For workspaces whose packages resolve against built artifacts (for example dist/ output consumed via workspace aliases), run the repository build (for example npm run build) after install. Full-suite validation and commit hooks fail on stale or missing artifacts with errors that look like code regressions. State when the build was skipped and why.
  5. If no dependency manager is clearly detectable, continue and state what was checked.

Output

End with:

  • Active workdir.
  • Branch name.
  • Whether worktree or no-worktree mode is active.
  • Dependency bootstrap command run, or why it was skipped.
  • Workspace build command run (when applicable), or why it was skipped.
  • Any workspace risks or blockers.

© codeaholicguy, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/dev-worktree of codeaholicguy/ai-devkit.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 7ef0cd5

Compare with similar skills

Dev Worktree next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dev Worktree compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dev Worktree this skillcodeaholicguy/ai-devkit1.6k—~980Automated safety check: PassApache-2.0
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Finishing A Development Branchfarm-fe/farm5.6k34 repos~1.8kAutomated safety check: PassMIT
Git Worktree Cleanuplobehub/lobehub83k—~2.8kAutomated safety check: PassCustom licence
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
Ccmanager Configkbwo/ccmanager1.3k—~1.5kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…

    5.6k GitHub starsUsed in 34 repos~1.8k tokens
    DevelopmentAuto-check passed
  • Git Worktree Cleanup

    lobehub/lobehub

    Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.

    83k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Ccmanager Config

    kbwo/ccmanager

    Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global ~/.config/ccmanager/config.json.

    1.3k GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Builds a Cap feature in an isolated Git worktree with disposable dev resources, verification, a recorded demo and a neutral pull request, started with /building.

    23k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check: warnings

More from codeaholicguy/ai-devkit

All 28 skills in this repo
  • Agent Management

    codeaholicguy/ai-devkit

    AI DevKit · Manage running AI agents with ai-devkit agent commands.

    1.6k GitHub stars~558 tokensUpdated today
    Auto-check passed
  • Dev Lifecycle

    codeaholicguy/ai-devkit

    AI DevKit · Orchestrator for structured SDLC phase skills. An agent skill from codeaholicguy/ai-devkit.

    1.6k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Task

    codeaholicguy/ai-devkit

    AI DevKit · Track dev-lifecycle / structured-debug progress on a durable task with the ai-devkit task CLI.

    1.6k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Simplify Implementation

    codeaholicguy/ai-devkit

    AI DevKit · Analyze and simplify existing implementations to reduce complexity, improve maintainability, and enhance scalability.

    1.6k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Agent Communication

    codeaholicguy/ai-devkit

    AI DevKit · Exchange information with active Codex, Claude Code, and other AI agents using ai-devkit agent list, detail, and send.

    1.6k GitHub stars~321 tokensUpdated today
    Auto-check passed
  • Technical Writer

    codeaholicguy/ai-devkit

    AI DevKit · Review and improve documentation for novice users.

    1.6k GitHub stars~431 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Dev Worktree

What does Dev Worktree do?

AI DevKit · Worktree setup and resume guidance for isolated feature work. Dev Worktree is an agent skill from codeaholicguy/ai-devkit. AI DevKit · Worktree setup and resume guidance for isolated feature work.

When should I use Dev Worktree?

Dev Worktree fits situations like: verifying a feature branch/worktree for lifecycle; multi-agent workflows.

How do I install Dev Worktree in Claude Code?

Run `npx skills add codeaholicguy/ai-devkit --skill dev-worktree -a claude-code`. Or copy the skill folder (skills/dev-worktree in codeaholicguy/ai-devkit) into .claude/skills/dev-worktree in your project. Claude Code loads it when a task matches its description.

How do I install Dev Worktree in Codex?

Run `npx skills add codeaholicguy/ai-devkit --skill dev-worktree -a codex`. Or copy the skill folder (skills/dev-worktree in codeaholicguy/ai-devkit) into .agents/skills/dev-worktree in your project. Codex loads it when a task matches its description.

Can I use Dev Worktree in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add codeaholicguy/ai-devkit --skill dev-worktree -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dev-worktree, .gemini/skills/dev-worktree, .github/skills/dev-worktree and .opencode/skills/dev-worktree in your project.

What does Dev Worktree need to run?

Going by SKILL.md and its folder, Dev Worktree needs the command-line tools its instructions call (git, npm, cargo, pnpm, yarn and bun). Our summary lists: Python 3.

Does Dev Worktree access the network?

SKILL.md contains no URLs. Its commands use git, npm, uv and pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Dev Worktree safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dev Worktree use?

Dev Worktree is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dev Worktree use?

About 980 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dev Worktree?

Skills that share tags, products or a category with Dev Worktree: Finishing a Development Branch (obra/superpowers, 296k stars), Finishing A Development Branch (farm-fe/farm, 5.6k stars), Git Worktree Cleanup (lobehub/lobehub, 83k stars) and Pre-Release PR Triage (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dev Worktree?

codeaholicguy (a GitHub user) maintains it in codeaholicguy/ai-devkit, which has 1,642 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 7, 2026.

Source: codeaholicguy/ai-devkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.