Agent skill

Worktree

by bonny in bonny/WordPress-Simple-History

Creates an isolated git worktree with its own WordPress test environment.

No licenceAuto-check: notesDevelopment

Install Worktree

skills CLI
$ npx skills add bonny/WordPress-Simple-History --skill worktree -a claude-code

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

GitHub CLI
$ gh skill install bonny/WordPress-Simple-History 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/bonny/WordPress-Simple-History.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/worktree .claude/skills/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
worktree
GitHub stars
317
Token cost
~2.9k tokens
SKILL.md length
1,141 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
None found

At a glance

Creates an isolated git worktree with its own WordPress test environment.

  • Works in 2 steps: Create the worktree → Start Playground (mandatory — do this…
  • Working on multi-day features
  • SKILL.md covers Quick Path:…, Checks and tests inside a…, When to Use Worktrees and Creating a Worktree, plus 4 more sections
  • Calls git, jq and curl; needs WP_ADMIN_PASSWORD

What it does

Worktree is an agent skill from bonny/WordPress-Simple-History. Creates an isolated git worktree with its own WordPress test environment. Use when working on multi-day features or risky changes needing parallel testing.

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git worktrees. It works with WordPress and Git. The repository describes itself as: 🔍🕵️♀️ WordPress audit log that track user changes in WordPress admin using a nice activity feed.

When your agent uses it

  • Working on multi-day features
  • Risky changes needing parallel testing

Example prompts

  • “Use the worktree skill to create an isolated git worktree with its own WordPress test environment”
  • “/worktree”

Requirements

  • Node.js
  • Docker
  • Pre-approved tools (allowed-tools): Bash, Read, Write, Edit, Glob

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. Create the worktree
  2. Start Playground (mandatory — do this immediately)

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Write
    • Edit
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • jq
    • curl
    • npm
    • npx
    • docker

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

  • Network

    No URLs in SKILL.md. Its commands use git, curl, npm, npx and docker, 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 these keys or tokens, usually read from environment variables:

    • WP_ADMIN_PASSWORD

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

Context cost

Worktree loads about 2.9k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 1,141 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Write, Edit, Glob

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

Without a licence we can't republish the file, so here is its outline and opening line. It has 1,141 words (~2,868 tokens).

“Use git worktrees for issues that require extended development (multiple days, risky changes, or parallel feature work). Each worktree gets its own branch, dependencies, and a WordPress test site.”

— opening of SKILL.md by bonny
name
worktree
allowed-tools
Bash, Read, Write, Edit, Glob
disable-model-invocation
false

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/worktree of bonny/WordPress-Simple-History.

Open the folder on GitHubat commit 24f337f

Compare with similar skills

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.

Worktree compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Worktree this skillbonny/WordPress-Simple-History317—~2.9kAutomated safety check: NotesNone
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 bonny/WordPress-Simple-History

All 21 skills in this repo
  • Blueprint

    bonny/WordPress-Simple-History

    A skill your agent uses when the deliverable is WordPress Playground Blueprint JSON or a Blueprint bundle, including creating, editing, reviewing, validating schema keys, choosing steps/resources…

    317 GitHub starsUsed in 1 repo~4k tokens
    Auto-check passed
  • Action Links

    bonny/WordPress-Simple-History

    Guides implementation of structured action links on log events.

    317 GitHub stars~3.7k tokensUpdated today
    Auto-check passed
  • Changelog

    bonny/WordPress-Simple-History

    Adds changelog entries to readme.txt following keepachangelog format.

    317 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Code Quality

    bonny/WordPress-Simple-History

    Runs linting and static analysis on PHP/CSS/JS using phpcs, phpstan, and rector.

    317 GitHub stars~519 tokensUpdated today
    Auto-check: notes
  • Create Logger

    bonny/WordPress-Simple-History

    Guides creation of custom loggers for Simple History. An agent skill from bonny/WordPress-Simple-History.

    317 GitHub stars~3.7k tokensUpdated today
    Auto-check: notes
  • Logger Messages

    bonny/WordPress-Simple-History

    Enforces active voice for logger messages and the Event Details API.

    317 GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Worktree

What does Worktree do?

Creates an isolated git worktree with its own WordPress test environment. Worktree is an agent skill from bonny/WordPress-Simple-History. Creates an isolated git worktree with its own WordPress test environment.

When should I use Worktree?

Worktree fits situations like: working on multi-day features; risky changes needing parallel testing.

How do I install Worktree in Claude Code?

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

How do I install Worktree in Codex?

Run `npx skills add bonny/WordPress-Simple-History --skill worktree -a codex`. Or copy the skill folder (.claude/skills/worktree in bonny/WordPress-Simple-History) into .agents/skills/worktree in your project. Codex loads it when a task matches its description.

Can I use 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 bonny/WordPress-Simple-History --skill 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/worktree, .gemini/skills/worktree, .github/skills/worktree and .opencode/skills/worktree in your project.

What does Worktree need to run?

Going by SKILL.md and its folder, Worktree needs the command-line tools its instructions call (git, jq, curl, npm, npx and docker) and credentials named WP_ADMIN_PASSWORD. Our summary lists: Node.js; Docker. Its frontmatter pre-approves these tools: Bash, Read, Write, Edit, Glob.

Does Worktree access the network?

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

Is Worktree safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Worktree use?

No licence was found for Worktree or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Worktree use?

About 2.9k tokens (SKILL.md is roughly 11k 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 Worktree?

Skills that share tags, products or a category with 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 Worktree?

bonny (a GitHub user) maintains it in bonny/WordPress-Simple-History, which has 317 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 7, 2026.

Source: bonny/WordPress-Simple-History on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.