بنقرة واحدة
speckit-worktrees-list
Dashboard of all active worktrees with spec-artifact and task progress
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Dashboard of all active worktrees with spec-artifact and task progress
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate a custom checklist for the current feature based on user requirements.
Identify underspecified areas in the current feature spec by asking up
Run a budget-aware exploration loop that externalizes every finding into the harness state files
Initialize externalized harness state (budget, candidates, curated set, evidence, verification, observations) for the active feature
Synthesize curated evidence and verification records into the feature's research.md with a coverage table
Render a compact, budget-aware slice of the harness state with a recommended next action
| name | speckit-worktrees-list |
| description | Dashboard of all active worktrees with spec-artifact and task progress |
| compatibility | Requires spec-kit project structure with .specify/ directory |
| metadata | {"author":"github-spec-kit","source":"worktrees:commands/speckit.worktrees.list.md"} |
Show all active git worktrees with their feature branch status, spec artifact availability, and task completion progress.
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty). The user may request:
compact — one-line-per-worktree summarystale — show only stale/idle worktreesgit worktree list returns resultsList all worktrees: Run git worktree list --porcelain and parse the output.
Extract for each worktree: path, branch, HEAD commit, prunable status.
Identify the primary checkout vs. linked worktrees.
Read config: Load layout from worktree-config.yml to determine whether to look for worktrees in .worktrees/ (nested) or sibling directories (sibling). For sibling layout, also list directories matching the sibling pattern ../<repo>--*.
Gather feature status per worktree:
specs/<branch>/ for spec.md, plan.md, tasks.md, research.md, data-model.mdspecs/<branch>/tasks.md exists, count - [x] vs - [ ] linesgit log -1 --format='%ar' <branch> (e.g., "2 hours ago")git branch --merged main | grep <branch>git -C <worktree-path> status --porcelain | wc -lClassify status:
| Status | Condition |
|---|---|
| Active | Commits within 7 days, unmerged |
| Idle | No commits for 7-30 days, unmerged |
| Stale | No commits for 30+ days, unmerged |
| Merged | Branch merged into main/master |
| Orphaned | Branch deleted but worktree exists |
Output dashboard:
## Active Worktrees
| # | Branch | Path | Status | Artifacts | Tasks | Last Activity | Dirty |
|---|--------|------|--------|-----------|-------|---------------|-------|
| 1 | 003-user-auth | ../MyProject--003-user-auth | Active | spec plan tasks | 12/18 (67%) | 2h ago | 3 files |
| 2 | 005-api-gateway | ../MyProject--005-api-gateway | Merged | spec plan tasks | 8/8 (100%) | 3d ago | clean |
**Summary**: 2 worktrees + primary checkout | 1 ready to clean (merged)
**Recommended actions:**
- Run `/speckit.worktrees.clean` to remove merged worktree (005-api-gateway)