Skip to content
Back to skills

Aetox Worktree

BSecurity

ตอนจะเริ่มงานฟีเจอร์ที่ไม่ควรไปยุ่งกับ checkout ปัจจุบันของผู้ใช้ หรือจะรันแผนที่มีหลายคอมมิต

  • 46 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
ai-agentsgogit

Security analysis

B84/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned September 27, 2026

npx -y skills add Mikedev115/Aetox --skill aetox-worktree --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Aetox Worktree?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Aetox Worktree
[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/mikedev115-aetox-worktree/badge)](https://www.skillsdirectory.com/skills/mikedev115-aetox-worktree)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: aetox-worktree
before: starting feature work that must not disturb the user's current checkout, or running a plan that will make many commits
description: ตอนจะเริ่มงานฟีเจอร์ที่ไม่ควรไปยุ่งกับ checkout ปัจจุบันของผู้ใช้ หรือจะรันแผนที่มีหลายคอมมิต
source: https://github.com/obra/superpowers (using-git-worktrees), adapted
license: MIT
copyright: Copyright (c) 2026 Aetox Skills
---

# Aetox Worktree

Work that will take many commits, or that must not touch what the user has
open, happens in a linked worktree on its own branch. Detect first, ask
second, create third.

## Detect

`git rev-parse --git-dir` and `git rev-parse --git-common-dir`: when they
differ, this is already a linked worktree (unless
`git rev-parse --show-superproject-working-tree` prints a path, which means a
submodule, not a worktree). Already isolated means do not make another; say
where you are and on which branch, and go to setup.

## Ask

Unless the user's instructions already say what they want, ask once:
"Set this up in an isolated worktree, so your current branch is untouched?"
No means work in place. A yes once is not a yes for the next job.

## Create

Where: the user's stated place; else an existing `.worktrees/` or
`worktrees/` at the project root; else `.worktrees/`. A project-local
folder must be ignored before anything is created in it: `git check-ignore`,
and if it is not, add it to `.gitignore` and commit that first, or the
worktree's contents end up in the repository.

Then `git worktree add <folder>/<branch> -b <branch>` and work from there. A
permission error means the sandbox refused; say so and work in place.

## Set up, then prove the baseline

Run the project's install (`npm install`, `go mod download`, `pip install
-r …`, whatever the files say) and the test suite once before changing
anything. A red baseline is reported before work starts, not discovered
after it, when it can no longer be told apart from the work.

## Leaving

The worktree is removed when the branch has been merged or pushed
(`aetox-finish-branch`), never before, and never with uncommitted work in
it.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…