using-git-worktrees
Skill0 starsChanged 3 months agoMITView on GitHub
Use when feature work needs isolation or an approved design is ready for implementation.
189 other projects use a version of this.
Adopted by
Most recently taken up by
- DemonDamon/AgenticXtheir own version, first seen Nov 9, 2026
- chrysogonus/power-agentstheir own version, first seen Nov 8, 2026
- roundpilot/superpowers-antigravitytheir own version, first seen Nov 8, 2026
- REPOZY/superpowers-optimizedtheir own version, first seen Nov 8, 2026
- lingyired/status-triotheir own version, first seen Nov 8, 2026
- afawfawffaf/my-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Leodorareluctant259Skillchinese-code-review
中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈
Also in 8 projects that use this
Leodorareluctant259Skillchinese-commit-conventions
中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化
Also in 8 projects that use this
obraSkilldiagnosing-superpowers
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
Also in 20 projects that use this
frankxaiSkilldefense-in-depth
Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible
Also in 4 projects that use this
xfstudioSkilltest-fixing
Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.
Also in 3 projects that use this
kntismSkillcondition-based-waiting
Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses
Also in 3 projects that use this
- +3 more from Leodorareluctant259
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 189
- obra/superpowers★ 314ksame name
- jnMetaCode/superpowers-zh★ 8.4ksame name
- openai/plugins★ 7.8ksame name
- farm-fe/farm★ 5.6ksame name
- microsoft/FluidFramework★ 4.9ksame name
- silvertakana/worldwideview★ 1.9ksame name
- lingyired/status-trio★ 1.8ksame name
- GanyuanRan/Aegis★ 1.4ksame name
- pcvelz/superpowers★ 1.3ksame name
- DemonDamon/AgenticX★ 1ksame name
179 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- design-reviewSkill
- dispatching-parallel-agentsSkill
- executing-designSkill
- finding-unknownsSkill
- finishSkill
- managing-repo-standard-docsSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- using-groundworkSkill
- verification-before-completionSkill
- writing-for-juniorSkill
- writing-skillsSkill
The file
Files
using-git-worktrees
Execution contract
입력은 작업 목표와 제공된 브랜치·경로 지시다. 출력은 작업 경로·브랜치·격리 수단·정리 주체와 시작 시점의 검증 결과다. 경로는 시작 리포 루트 기준이며, 준비 뒤의 검증은 작업 워크스페이스에서 실행한다.
Detect and prepare isolation
git rev-parse --git-dir, --git-common-dir, --show-superproject-working-tree와 현재 브랜치를 확인한다. git 디렉터리와 공통 디렉터리의 실제 경로가 다르고 서브모듈이 아니면 연결된 워크트리다. 호스트가 이미 제공한 격리는 재사용하고 관리 주체를 기록한다.
사용자가 지정한 작업 방식·브랜치·경로를 따른다. 지정하지 않은 이름과 위치는 작업에서 정해 알리며, 작업 격리 자체를 허락받는 절차는 두지 않는다.
새 격리가 필요하면 실행 환경의 네이티브 워크트리 도구를 우선하고, 없으면 git worktree add를 쓴다.
수동 워크트리의 경로는 명시 지시 → 기존 .worktrees/ → 기존 worktrees/ → .worktrees/ 순으로 고른다. 리포 내부 경로는 생성 전에 git check-ignore로 선택한 경로의 제외 여부를 확인한다. 제외되지 않았으면 .gitignore에 반영한다.
생성한 워크트리의 경로·브랜치·생성 주체를 기록해 finish에 넘긴다. 디렉터리 이름만으로 기존 워크트리를 에이전트 소유로 간주하지 않는다.
생성이 실패하면 원인을 조사한다. 제공된 작업 트리나 기능 브랜치에서 안전하게 진행할 수 있으면 사유를 알리고 사용한다. 사용자 지시 없이 main·master에서 구현하거나 기존 변경을 덮어쓰지 않는다.
Set up and verify the baseline
리포 지침·잠금 파일·CI에서 필요한 셋업과 검증 명령을 확인한다. 파일 확장자만 보고 여러 패키지 관리자의 설치를 실행하지 않는다.
이번 변경과 관련된 시작 상태를 검증한다. 실패는 원인을 조사해 기존 문제와 작업의 막힘을 구분하고, 변경과 무관한 실패는 증거를 남긴 채 진행할 수 있다.
검증 방법은 에이전트가 정한다. 서비스의 완료 기준 자체가 미정일 때는 groundwork:finding-unknowns로 사용자와 결정한다.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

