Codex App 兼容性实施计划
Section titled “Codex App 兼容性实施计划”对于 agentic workers: REQUIRED SUB-SKILL: 使用 superpowers:subagent-driven-development (推荐) or superpowers:executing-plans to implement this 计划 task-by-task. Steps use checkbox (
- [ ]) syntax for tracking.
Goal: Make using-git-worktrees, finishing-a-development-branch, and related skills work in the Codex App’s sandboxed worktree environment without breaking 现有 behavior.
架构: Read-only environment detection (git-dir vs git-common-dir) at the 启动 of two skills. 如果 already in a 链接 worktree, 跳过 creation. 如果 on 分离 HEAD, emit a handoff payload instead of the 4-option menu. Sandbox 回退 catches permission 错误 during worktree creation.
Tech Stack: Git, Markdown (skill files are instruction documents, not executable code)
Spec: docs/superpowers/specs/2026-03-23-codex-app-compatibility-design.md
File Structure
Section titled “File Structure”| File | Responsibility | Action |
|---|---|---|
skills/using-git-worktrees/SKILL.md | Worktree creation + isolation | 添加 步骤 0 detection + sandbox 回退 |
skills/finishing-a-development-branch/SKILL.md | Branch finishing 工作流 | 添加 步骤 1.5 detection + 清理 guard |
skills/subagent-driven-development/SKILL.md | Plan execution with subagents | 更新 Integration description |
skills/executing-plans/SKILL.md | Plan execution inline | 更新 Integration description |
skills/using-superpowers/references/codex-tools.md | Codex 平台 引用 | 添加 detection + finishing docs |
Task 1: 添加 步骤 0 to using-git-worktrees
Section titled “Task 1: 添加 步骤 0 to using-git-worktrees”文件:
-
修改:
skills/using-git-worktrees/SKILL.md:14-15(insert after 概览, before Directory Selection Process) -
步骤 1: Read the 当前 skill file
Read skills/using-git-worktrees/SKILL.md in full. Identify the exact insertion point: after the “Announce at 启动” line (line 14) and before ”## Directory Selection Process” (line 16).
- 步骤 2: Insert 步骤 0 section
Insert the following between the 概览 section and ”## Directory Selection Process”:
## Step 0: Check if Already in an Isolated Workspace
Before creating a worktree, check if one already exists:
```bashGIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)BRANCH=$(git branch --show-current)If GIT_DIR differs from GIT_COMMON: You are already inside a linked worktree (created by the Codex App, Claude Code’s Agent tool, a previous skill run, or the user). Do NOT create another worktree. Instead:
- Run project setup (auto-detect package manager as in “Run Project Setup” below)
- Verify clean baseline (run tests as in “Verify Clean Baseline” below)
- Report with branch state:
- On a branch: “Already in an isolated workspace at
<path>on branch<name>. Tests passing. Ready to implement.” - Detached HEAD: “Already in an isolated workspace at
<path>(detached HEAD, externally managed). Tests passing. Note: branch creation needed at finish time. Ready to implement.”
- On a branch: “Already in an isolated workspace at
After reporting, STOP. Do not continue to Directory Selection or Creation Steps.
If GIT_DIR equals GIT_COMMON: Proceed with the full worktree creation flow below.
Sandbox fallback: If you proceed to Creation Steps but git worktree add -b fails with a permission error (e.g., “Operation not permitted”), treat this as a late-detected restricted environment. Fall back to the behavior above — run setup and baseline tests in the current directory, report accordingly, and STOP.
- [ ] **步骤 3: 验证 the insertion**
Read the file again. Confirm:- 步骤 0 appears between 概览 and Directory Selection Process- The rest of the file (Directory Selection, Safety 验证, Creation Steps, etc.) is unchanged- No duplicate sections or broken markdown
- [ ] **步骤 4: 提交**
```bashgit add skills/using-git-worktrees/SKILL.mdgit commit -m "feat(using-git-worktrees): add Step 0 environment detection (PRI-823)
Skip worktree creation when already in a linked worktree. Includessandbox fallback for permission errors on git worktree add."Task 2: 更新 using-git-worktrees Integration section
Section titled “Task 2: 更新 using-git-worktrees Integration section”文件:
-
修改:
skills/using-git-worktrees/SKILL.md:211-215(Integration > Called by) -
步骤 1: 更新 the three “Called by” entries
Change lines 212-214 from:
- **brainstorming** (Phase 4) - REQUIRED when design is approved and implementation follows- **subagent-driven-development** - REQUIRED before executing any tasks- **executing-plans** - REQUIRED before executing any tasks改为:
- **brainstorming** - REQUIRED: Ensures isolated workspace (creates one or verifies existing)- **subagent-driven-development** - REQUIRED: Ensures isolated workspace (creates one or verifies existing)- **executing-plans** - REQUIRED: Ensures isolated workspace (creates one or verifies existing)- 步骤 2: 验证 the Integration section
Read the Integration section. Confirm all three entries are updated, “Pairs with” is unchanged.
- 步骤 3: 提交
git add skills/using-git-worktrees/SKILL.mdgit commit -m "docs(using-git-worktrees): update Integration descriptions (PRI-823)
Clarify that skill ensures a workspace exists, not that it always creates one."Task 3: 添加 步骤 1.5 to finishing-a-development-branch
Section titled “Task 3: 添加 步骤 1.5 to finishing-a-development-branch”文件:
-
修改:
skills/finishing-a-development-branch/SKILL.md:38(insert after 步骤 1, before 步骤 2) -
步骤 1: Read the 当前 skill file
Read skills/finishing-a-development-branch/SKILL.md in full. Identify the insertion point: after “如果 tests pass: Continue to 步骤 2.” (line 38) and before ”### 步骤 2: Determine Base Branch” (line 40).
- 步骤 2: Insert 步骤 1.5 section
Insert the following between 步骤 1 and 步骤 2:
### Step 1.5: Detect Environment
```bashGIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)BRANCH=$(git branch --show-current)Path A — GIT_DIR differs from GIT_COMMON AND BRANCH is empty (externally managed worktree, detached HEAD):
First, ensure all work is staged and committed (git add + git commit).
Then present this to the user (do NOT present the 4-option menu):
Implementation complete. All tests passing.Current HEAD: <full-commit-sha>
This workspace is 外部管理 (分离 HEAD).I cannot create branches, push, or open PRs from here.
⚠ These commits are on a detached HEAD. 如果 you do not create a branch,they may be lost when this workspace is cleaned up.
如果 your host application 提供 these controls:- "创建 branch" — to name a branch, then commit/push/PR- "Hand off to 本地" — to move changes to your 本地 checkout
Suggested 分支名: <ticket-id/short-description>Suggested 提交消息: <summary-of-work>Branch name: use ticket ID if available (e.g., pri-823/codex-compat), otherwise slugify the first 5 words of the plan title, otherwise omit. Avoid sensitive content in branch names.
Skip to Step 5 (cleanup is a no-op — see guard below).
Path B — GIT_DIR differs from GIT_COMMON AND BRANCH exists (externally managed worktree, named branch):
Proceed to Step 2 and present the 4-option menu as normal.
Path C — GIT_DIR equals GIT_COMMON (normal environment):
Proceed to Step 2 and present the 4-option menu as normal.
- [ ] **步骤 3: 验证 the insertion**
Read the file again. Confirm:- 步骤 1.5 appears between 步骤 1 and 步骤 2- Steps 2-5 are unchanged- Path A handoff includes commit SHA and data loss 警告- Paths B and C proceed to 步骤 2 normally
- [ ] **步骤 4: 提交**
```bashgit add skills/finishing-a-development-branch/SKILL.mdgit commit -m "feat(finishing-a-development-branch): add Step 1.5 environment detection (PRI-823)
Detect externally managed worktrees with detached HEAD and emit handoffpayload instead of 4-option menu. Includes commit SHA and data loss warning."Task 4: 添加 步骤 5 清理 guard to finishing-a-development-branch
Section titled “Task 4: 添加 步骤 5 清理 guard to finishing-a-development-branch”文件:
-
修改:
skills/finishing-a-development-branch/SKILL.md(步骤 5: Cleanup Worktree — find by section heading, line numbers will have shifted after Task 3) -
步骤 1: Read the 当前 步骤 5 section
Find the ”### 步骤 5: Cleanup Worktree” section in skills/finishing-a-development-branch/SKILL.md (line numbers will have shifted after Task 3’s insertion). The 当前 步骤 5 is:
### Step 5: Cleanup Worktree
**For Options 1, 2, 4:**
Check if in worktree:```bashgit worktree list | grep $(git branch --show-current)If yes:
git worktree remove <worktree-path>For Option 3: Keep worktree.
- [ ] **步骤 2: 添加 the 清理 guard before 现有 logic**
替换 the 步骤 5 section with:
```markdown### Step 5: Cleanup Worktree
**First, check if worktree is externally managed:**
```bashGIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)If GIT_DIR differs from GIT_COMMON: skip worktree removal — the host environment owns this workspace.
Otherwise, for Options 1 and 4:
Check if in worktree:
git worktree list | grep $(git branch --show-current)If yes:
git worktree remove <worktree-path>For Option 3: Keep worktree.
Note: the original text said "对于 Options 1, 2, 4" but the Quick Reference table and Common Mistakes section say "Options 1 & 4 only." This edit aligns 步骤 5 with those sections.
- [ ] **步骤 3: 验证 the replacement**
Read 步骤 5. Confirm:- Cleanup guard (re-detection) appears first- Existing removal logic preserved for non-externally-managed worktrees- "Options 1 and 4" (not "1, 2, 4") matches Quick Reference and Common Mistakes
- [ ] **步骤 4: 提交**
```bashgit add skills/finishing-a-development-branch/SKILL.mdgit commit -m "feat(finishing-a-development-branch): add Step 5 cleanup guard (PRI-823)
Re-detect externally managed worktree at cleanup time and skip removal.Also fixes pre-existing inconsistency: cleanup now correctly saysOptions 1 and 4 only, matching Quick Reference and Common Mistakes."Task 5: 更新 Integration lines in subagent-driven-development and executing-plans
Section titled “Task 5: 更新 Integration lines in subagent-driven-development and executing-plans”文件:
-
修改:
skills/subagent-driven-development/SKILL.md:268 -
修改:
skills/executing-plans/SKILL.md:68 -
步骤 1: 更新
subagent-driven-development
Change line 268 from:
- **superpowers:using-git-worktrees** - REQUIRED: Set up isolated workspace before starting改为:
- **superpowers:using-git-worktrees** - REQUIRED: Ensures isolated workspace (creates one or verifies existing)- 步骤 2: 更新
executing-plans
Change line 68 from:
- **superpowers:using-git-worktrees** - REQUIRED: Set up isolated workspace before starting改为:
- **superpowers:using-git-worktrees** - REQUIRED: Ensures isolated workspace (creates one or verifies existing)- 步骤 3: 验证 both files
Read line 268 of skills/subagent-driven-development/SKILL.md and line 68 of skills/executing-plans/SKILL.md. Confirm both say “Ensures 隔离工作区 (creates one or verifies 现有)”.
- 步骤 4: 提交
git add skills/subagent-driven-development/SKILL.md skills/executing-plans/SKILL.mdgit commit -m "docs(sdd, executing-plans): update worktree Integration descriptions (PRI-823)
Clarify that using-git-worktrees ensures a workspace exists rather thanalways creating one."Task 6: 添加 environment detection docs to codex-tools.md
Section titled “Task 6: 添加 environment detection docs to codex-tools.md”文件:
-
修改:
skills/using-superpowers/references/codex-tools.md:25(append at end) -
步骤 1: Read the 当前 file
Read skills/using-superpowers/references/codex-tools.md in full. Confirm it ends at line 25-26 after the multi_agent section.
- 步骤 2: Append two 新 sections
添加 at the end of the file:
## Environment Detection
Skills that create worktrees or finish branches should detect theirenvironment with read-only git commands before proceeding:
```bashGIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)BRANCH=$(git branch --show-current)GIT_DIR != GIT_COMMON→ already in a linked worktree (skip creation)BRANCHempty → detached HEAD (cannot branch/push/PR from sandbox)
See using-git-worktrees Step 0 and finishing-a-development-branch
Step 1.5 for how each skill uses these signals.
Codex App Finishing
Section titled “Codex App Finishing”When the sandbox blocks branch/push operations (detached HEAD in an externally managed worktree), the agent commits all work and informs the user to use the App’s native controls:
- “Create branch” — names the branch, then commit/push/PR via App UI
- “Hand off to local” — transfers work to the user’s local checkout
The agent can still run tests, stage files, and output suggested branch names, commit messages, and PR descriptions for the user to copy.
- [ ] **步骤 3: 验证 the additions**
Read the full file. Confirm:- Two 新 sections appear after the 现有 content- Bash code block renders correctly (not escaped)- Cross-references to 步骤 0 and 步骤 1.5 are present
- [ ] **步骤 4: 提交**
```bashgit add skills/using-superpowers/references/codex-tools.mdgit commit -m "docs(codex-tools): add environment detection and App finishing docs (PRI-823)
Document the git-dir vs git-common-dir detection pattern and the CodexApp's native finishing flow for skills that need to adapt."Task 7: Automated test — environment detection
Section titled “Task 7: Automated test — environment detection”文件:
-
创建:
tests/codex-app-compat/test-environment-detection.sh -
步骤 1: 创建 test 目录
mkdir -p tests/codex-app-compat- 步骤 2: Write the detection test script
创建 tests/codex-app-compat/test-environment-detection.sh:
#!/usr/bin/env bashset -euo pipefail
# Test environment detection logic from PRI-823# Tests the git-dir vs git-common-dir comparison used by# using-git-worktrees Step 0 and finishing-a-development-branch Step 1.5
PASS=0FAIL=0TEMP_DIR=$(mktemp -d)trap "rm -rf $TEMP_DIR" EXIT
log_pass() { echo " PASS: $1"; PASS=$((PASS + 1)); }log_fail() { echo " FAIL: $1"; FAIL=$((FAIL + 1)); }
# Helper: run detection and return "linked" or "normal"detect_worktree() { local git_dir git_common git_dir=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P) git_common=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P) if [ "$git_dir" != "$git_common" ]; then echo "linked" else echo "normal" fi}
echo "=== Test 1: Normal repo detection ==="cd "$TEMP_DIR"git init test-repo > /dev/null 2>&1cd test-repogit commit --allow-empty -m "init" > /dev/null 2>&1result=$(detect_worktree)if [ "$result" = "normal" ]; then log_pass "Normal repo detected as normal"else log_fail "Normal repo detected as '$result' (expected 'normal')"fi
echo "=== Test 2: Linked worktree detection ==="git worktree add "$TEMP_DIR/test-wt" -b test-branch > /dev/null 2>&1cd "$TEMP_DIR/test-wt"result=$(detect_worktree)if [ "$result" = "linked" ]; then log_pass "Linked worktree detected as linked"else log_fail "Linked worktree detected as '$result' (expected 'linked')"fi
echo "=== Test 3: Detached HEAD detection ==="git checkout --detach HEAD > /dev/null 2>&1branch=$(git branch --show-current)if [ -z "$branch" ]; then log_pass "Detached HEAD: branch is empty"else log_fail "Detached HEAD: branch is '$branch' (expected empty)"fi
echo "=== Test 4: Linked worktree + detached HEAD (Codex App simulation) ==="result=$(detect_worktree)branch=$(git branch --show-current)if [ "$result" = "linked" ] && [ -z "$branch" ]; then log_pass "Codex App simulation: linked + detached HEAD"else log_fail "Codex App simulation: result='$result', branch='$branch'"fi
echo "=== Test 5: Cleanup guard — linked worktree should NOT remove ==="cd "$TEMP_DIR/test-wt"result=$(detect_worktree)if [ "$result" = "linked" ]; then log_pass "Cleanup guard: linked worktree correctly detected (would skip removal)"else log_fail "Cleanup guard: expected 'linked', got '$result'"fi
echo "=== Test 6: Cleanup guard — main repo SHOULD remove ==="cd "$TEMP_DIR/test-repo"result=$(detect_worktree)if [ "$result" = "normal" ]; then log_pass "Cleanup guard: main repo correctly detected (would proceed with removal)"else log_fail "Cleanup guard: expected 'normal', got '$result'"fi
# Cleanup worktree before temp dir removalcd "$TEMP_DIR/test-repo"git worktree remove "$TEMP_DIR/test-wt" > /dev/null 2>&1 || true
echo ""echo "=== Results: $PASS passed, $FAIL failed ==="if [ "$FAIL" -gt 0 ]; then exit 1fi- 步骤 3: Make it executable and run it
chmod +x tests/codex-app-compat/test-environment-detection.sh./tests/codex-app-compat/test-environment-detection.sh预期 output: 6 passed, 0 failed.
- 步骤 4: 提交
git add tests/codex-app-compat/test-environment-detection.shgit commit -m "test: add environment detection tests for Codex App compat (PRI-823)
Tests git-dir vs git-common-dir comparison in normal repo, linkedworktree, detached HEAD, and cleanup guard scenarios."Task 8: Final 验证
Section titled “Task 8: Final 验证”文件:
-
Read: all 5 modified skill files
-
步骤 1: 运行 the automated detection tests
./tests/codex-app-compat/test-environment-detection.sh预期: 6 passed, 0 failed.
- 步骤 2: Read each modified file and verify changes
Read each file end-to-end:
-
skills/using-git-worktrees/SKILL.md— 步骤 0 present, rest unchanged -
skills/finishing-a-development-branch/SKILL.md— 步骤 1.5 present, 清理 guard present, rest unchanged -
skills/subagent-driven-development/SKILL.md— line 268 updated -
skills/executing-plans/SKILL.md— line 68 updated -
skills/using-superpowers/references/codex-tools.md— two 新 sections at end -
步骤 3: 验证 no unintended changes
git diff --stat HEAD~7Should show exactly 6 files changed (5 skill files + 1 test file). No other files modified.
- 步骤 4: 运行 现有 test suite
如果 test runner exists:
# Run skill-triggering tests# Note: tests/skill-triggering/ was lifted into drill scenarios on 2026-05-06.# See evals/scenarios/triggering-*.yaml. The reference below is a dated artifact../tests/skill-triggering/run-all.sh 2>/dev/null || echo "Skill triggering tests not available in this environment"
# Run SDD integration test./tests/claude-code/test-subagent-driven-development-integration.sh 2>/dev/null || echo "SDD integration test not available in this environment"Note: these tests require Claude Code with --dangerously-skip-permissions. 如果 not 可用, document that regression tests should be run manually.