Skip to content
TrustedSkillsbeta
Back to all skills

Create Worktree

Checked
shikajiro·vlatest·backend

Creates isolated Git worktrees for experimentation without affecting your main repository's history.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add shikajiro/claude-code-skill-example --skill create-worktree -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

shikajiro

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned shikajiro/claude-code-skill-example at f58c2e5240.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
3 files, 373 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The create-worktree skill allows an AI agent to create a new Git worktree. This is useful for switching between branches or working on multiple features simultaneously without affecting the main codebase. It essentially creates a separate, independent copy of your repository's working directory.

When to use it

  • You need to test a feature branch while continuing development on another branch.
  • You want to work on bug fixes in one branch while keeping your primary development environment clean.
  • A developer requests you create a new workspace for them based on a specific commit or branch.
  • You're debugging an issue and need to reproduce it in a separate working directory.

Key capabilities

  • Creates a new Git worktree.
  • Allows switching between branches within the new worktree.
  • Provides isolation from the main codebase.

Example prompts

  • "Create a new worktree named 'feature-x'."
  • "Make a worktree based on the release/1.0 branch."
  • "Can you create a worktree and checkout commit a1b2c3d4?"

Tips & gotchas

  • Requires Git to be installed and accessible in the environment where the AI agent is running.
  • Worktrees can consume significant disk space, especially for large repositories.