Skip to content
TrustedSkillsbeta
Back to all skills

Git Worktrees

Checked
jamesrochabrun·vlatest·backend·MIT

Manage multiple Git worktrees efficiently to isolate development branches and reduce repository clutter.

Repository

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 jamesrochabrun/skills --skill git-worktrees -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

jamesrochabrun

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 jamesrochabrun/skills at 2482c17637.

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

Commit
2482c17637
Manifest
skills/git-worktrees/SKILL.md
Scanned
8 files, 3,034 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

The git-worktrees skill enables AI agents to manage multiple parallel branches within a single Git repository without cluttering the main working directory. It allows agents to create, switch between, and delete worktrees, facilitating isolated development environments for different features or experiments.

When to use it

  • Isolating experimental code changes from the stable main branch to prevent accidental merges.
  • Managing parallel development of multiple features simultaneously within one repository.
  • Testing specific branches in a clean environment before integrating them back into the primary workflow.
  • Maintaining a tidy working directory by keeping unrelated tasks in separate worktrees rather than switching branches constantly.

Key capabilities

  • Creating new worktrees based on existing branches or commits.
  • Listing all available worktrees and their associated branch names.
  • Switching the active worktree to a specific path or branch.
  • Deleting unused worktrees to reclaim disk space and clean up the repository structure.

Example prompts

  • "Create a new worktree named 'feature-auth' based on the current HEAD for testing authentication logic."
  • "List all existing worktrees in this repository and show which branches they are tracking."
  • "Delete the old worktree at '/tmp/legacy-fix' as it is no longer needed."

Tips & gotchas

Ensure the AI agent has write permissions to the target directory, as creating or deleting worktrees modifies the filesystem. Be mindful of disk space usage when managing many concurrent worktrees, as each maintains its own copy of the checked-out files.