Skip to content
TrustedSkillsbeta
Back to all skills

Using Git Worktrees

Checked
obra·vlatest·backend·MIT

Efficiently manage multiple parallel development branches using Git worktrees to isolate changes and streamline workflows.

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 obra/superpowers --skill using-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

obra

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 obra/superpowers at 8ca22dba9a.

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

Commit
8ca22dba9a
Manifest
skills/using-git-worktrees/SKILL.md
Scanned
1 file, 152 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 using-git-worktrees skill enables AI agents to manage multiple Git branches within a single repository using Git worktrees. This allows users to checkout and switch between different branches without needing to commit changes or switch directories, streamlining workflows for developers working on parallel features or bug fixes.

When to use it

  • You need to work on multiple branches simultaneously in the same project.
  • You want to test changes from one branch while actively developing on another.
  • Your workflow requires frequent switching between feature branches without losing context.

Key capabilities

  • Checkout and manage multiple Git branches in parallel.
  • Avoid conflicts by isolating branch-specific changes.
  • Simplify development workflows for complex projects with many features.

Example prompts

  • "Set up a worktree for the 'feature-login' branch so I can test it alongside my current work."
  • "Create a new worktree for the 'bugfix-ui' branch and switch to it."
  • "Show me how to list all active Git worktrees in this repository."

Tips & gotchas

  • Ensure your Git version is 2.23 or newer, as worktrees require this feature.
  • Worktrees are tied to specific branches; avoid using them for unrelated tasks to prevent confusion.