flow-status
Flow: Status of Active Worktrees - Show all active worktrees with their issue, branch, dirty state, and PR status.
- License 许可
- MIT
- 所属仓库
- cooneycw/skillc
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- flow-status
- description
- Flow: Status of Active Worktrees - Show all active worktrees with their issue, branch, dirty state, and PR status.
03 SKILL.md 正文
<!-- GENERATED by claude-power-pack - scripts/codex-skill-sync.py; edit .claude/commands/flow/status.md instead -->
Codex harness adaptations
Generated from a Claude Code command. Where the procedure references these Claude-only surfaces, adapt as follows:
- Native worktrees (
EnterWorktree/ExitWorktreetool calls,.claude/worktrees/paths): use plain git instead, with the worktree as a VISIBLE SIBLING of the repo -git worktree add ../<repo>-<branch> -b <branch>(or$FLOW_WORKTREE_BASE/<repo>-<branch>when that env var is set), work inside it, thengit worktree remove ../<repo>-<branch>when done.
Flow: Status of Active Worktrees
Show all active worktrees with their issue, branch, dirty state, and PR status.
Instructions
When the user invokes /flow-status, perform these steps:
Step 1: Detect Repository
REPO=$(basename "$(git rev-parse --show-toplevel)")
Step 2: List Worktrees
git worktree list
Step 3: For Each Worktree, Gather State
For each worktree (skip the main repo entry):
# Get branch name
BRANCH=$(git -C "$WORKTREE_PATH" branch --show-current 2>/dev/null)
# Extract issue number from branch name (issue-N-*)
ISSUE_NUM=$(echo "$BRANCH" | grep -oP 'issue-\K[0-9]+' || echo "")
# Check for uncommitted changes
DIRTY=$(git -C "$WORKTREE_PATH" status --porcelain 2>/dev/null | wc -l)
# Check for unpushed commits
UNPUSHED=$(git -C "$WORKTREE_PATH" rev-list --count origin/main..HEAD 2>/dev/null || echo "0")
# Check PR status (if branch is pushed)
if [[ -n "$BRANCH" ]]; then
PR_INFO=$(gh pr list --head "$BRANCH" --json number,url,state --jq '.[0]' 2>/dev/null || echo "")
fi
Step 4: Fetch Issue Titles
For each detected issue number:
ISSUE_TITLE=$(gh issue view "$ISSUE_NUM" --json title --jq '.title' 2>/dev/null || echo "Unknown")
Step 5: Output
## Flow Status - {repo}
| Worktree | Issue | Branch | Status | PR |
|----------|-------|--------|--------|----|
| ../my-repo-issue-42-fix-login | #42 Fix login bug | issue-42-fix-login | 3 dirty files, 2 unpushed | - |
| ../my-repo-issue-55-add-tests | #55 Add tests | issue-55-add-tests | Clean | PR #78 (OPEN) |
### Suggestions
- **#42**: Has uncommitted work - commit or stash before switching
- **#55**: PR is open - check for reviews, then `/flow-merge`
Step 6: Detect Stale Branches
Check for local branches that may need cleanup:
# Count local issue-* branches with no active worktree
WORKTREE_BRANCHES=$(git worktree list --porcelain | grep "^branch " | sed 's|branch refs/heads/||')
STALE_COUNT=0
for branch in $(git branch | grep 'issue-' | sed 's/^[ *]*//'); do
echo "$WORKTREE_BRANCHES" | grep -q "^${branch}$" && continue
STALE_COUNT=$((STALE_COUNT + 1))
done
# Check for prunable worktree references
PRUNABLE=$(git worktree list --porcelain | grep -c "prunable" || echo "0")
If stale branches or prunable references exist, append to output:
### Cleanup Available
- {N} local issue branches with no active worktree
- {M} stale worktree references
Run `/flow-cleanup` to remove stale branches and references.
Notes
- Worktrees are visible siblings outside the repo (issue #627):
git worktree listshows them at<parent>/<repo>-<branch>, or under$FLOW_WORKTREE_BASEwhen set - not.claude/worktrees/ - Worktrees on
mainor non-issue branches are listed but marked as "(not issue-linked)" - If no worktrees exist besides main, report "No active worktrees. Run
/flow-start <issue>to begin." - Keep output concise - this is a quick status check
- Stale branch detection helps identify cleanup opportunities
04 同仓库更多 Skills
tiny-check
Run the tiny project check
tiny-check
A synthetic gate selection fixture.
flow-check
Use when you are asked to run a project's quality checks (tests, lint, type checks, security scan): runs them in one step and reports what failed, without committing.
flow-check
Use when you are asked to run a project's quality checks (tests, lint, type checks, security scan): runs them in one step and reports what failed, without committing.
flow-check
Use when you are asked to run a project's quality checks (tests, lint, type checks, security scan): runs them in one step and reports what failed, without committing.
flow-check
Use when you are asked to run a project's quality checks (tests, lint, type checks, security scan): runs them in one step and reports what failed, without committing.