Using Git Worktrees
ReviewAudited by ClawScan on May 1, 2026.
Overview
This is a coherent git-worktree helper, but users should know it may run local setup/test commands and create a small git commit during normal use.
Before installing, be comfortable with the agent creating git worktrees and branches, possibly committing a .gitignore update, and running project setup or test commands. For untrusted repositories, ask the agent to confirm before dependency installs, builds, tests, or commits.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may create a local git commit before starting the requested feature work.
The skill tells the agent to modify and commit repository files as part of setup. This is purpose-aligned safety behavior, but it is still a repository mutation users should notice.
If NOT ignored: ... 1. Add appropriate line to .gitignore 2. Commit the change 3. Proceed with worktree creation
If you want tighter control, ask the agent to show the .gitignore diff and get approval before committing.
Using the skill in an untrusted project could run dependency install scripts, builds, or tests on the local machine.
The documented workflow can run package-manager, build, and test commands. This is expected for preparing a development workspace, but those commands may execute project or dependency code.
Auto-detect and run appropriate setup: ... npm install ... cargo build ... pip install -r requirements.txt ... poetry install ... go mod download
Use it in projects you trust, or instruct the agent to ask before running dependency installation, build, or test commands.