AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Using Git Worktrees

skill-thiientv-godmode-using-git-worktrees · by thiientv

>-

No reviews yet
0 installs
17 views
0.0% view→install

Install

$ agentstack add skill-thiientv-godmode-using-git-worktrees

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-thiientv-godmode-using-git-worktrees)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
20d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Using Git Worktrees? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Using Git Worktrees

Isolation is a safety boundary, not a way to hide unreviewed changes.

Before creating one

  1. Inspect git status, current branch, repository root, and existing

worktrees.

  1. Preserve uncommitted user work; never reset, checkout, or clean it away.
  2. Choose an explicit branch name and a worktree path outside the main working

tree when practical.

  1. Confirm the base ref and whether ignored/generated files are needed.

Create safely

git worktree list
git worktree add ../- -b  

Run repository setup in the new worktree, record the exact base commit, and keep secrets and local environment files out of the branch. Do not use the same worktree for two writers.

Finish or discard

  • Review and test the branch before integrating it.
  • Merge or cherry-pick only the intended commits after checking the diff.
  • Remove a disposable worktree only after confirming its commits and needed

artifacts are preserved:

git worktree remove ../-
git worktree prune

Do not force removal when it contains unreviewed work. If a worktree is stale, inspect its branch and status before deciding whether it is recoverable.

Completion condition

The branch's base, ownership, integration path, and cleanup decision are explicit; the main checkout remains intact.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.