Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions skills/health/health.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ Shared routing context: `PyAutoBrain/skills/COMMANDS.md`.
| `/health check` | One-shot **green-light sweep**: sync each repo's `main`, run library pytest + workspace smoke, report a pass/fail matrix. | `PyAutoHeart/skills/health_sweep/reference.md` |
| `/health status` | **Active-work dashboard**: what's in flight across the repos (reads `active.md` / `planned.md` / `complete.md`), conflicts, idle repos. | `PyAutoHeart/skills/pyauto-status/reference.md` |
| `/health full` | **Release-run dashboard**: what the last PyAutoBuild release-prep run produced (per-workspace pass/fail/timing, slowest scripts, failure tracebacks). | `PyAutoHeart/skills/pyauto-status-full/reference.md` |
| `/health worktrees` | **Worktree/task dashboard**: every task worktree under `~/Code/PyAutoLabs-wt/`, cross-referenced with `active.md` — which parallel tasks are in flight and which repos each holds. | `PyAutoHeart/skills/worktree_status/reference.md` |

## Do

Expand All @@ -26,12 +27,14 @@ Shared routing context: `PyAutoBrain/skills/COMMANDS.md`.
`PyAutoHeart/skills/pyauto-status/reference.md`.
- **`/health full`** → follow the release-run dashboard procedure in
`PyAutoHeart/skills/pyauto-status-full/reference.md`.
- **`/health worktrees`** → follow the worktree dashboard procedure in
`PyAutoHeart/skills/worktree_status/reference.md`.

`/health` is the **only** health command. The former `/health_check`,
`/pyauto-status`, and `/pyauto-status-full` are retired as top-level commands and
live on as the `check`, `status`, and `full` legs above — the door is the Brain,
the procedures are Heart's.
`/pyauto-status`, `/pyauto-status-full`, and `/worktree_status` are retired as
top-level commands and live on as the `check`, `status`, `full`, and
`worktrees` legs above — the door is the Brain, the procedures are Heart's.

On the shell side, the same vocabulary applies: `health` (git-sync dashboard),
`health release`, and `health audit` (see `PyAutoMind/scripts/health.sh`) — a
`health release`, and `health audit` (see `PyAutoHeart/scripts/health.sh`) — a
separate local convenience layer, not this command.
4 changes: 2 additions & 2 deletions skills/repo_cleanup/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ execution-environment model: [`../WORKFLOW.md`](../WORKFLOW.md).
> Until it exists, run the reasoning here per this file and record the agent as a
> follow-up — the same pattern WORKFLOW.md describes for the other skills.

**Distinct from:** `worktree_status` (Heart read-only diagnostic — consulted here,
**Distinct from:** `/health worktrees` (Heart read-only diagnostic — consulted here,
but this also mutates); post-merge cleanup in `CLAUDE.md` (once per shipped task —
this covers residue when that flow is skipped); the start_dev branch survey
(task start — this is between-tasks hygiene).
Expand Down Expand Up @@ -104,6 +104,6 @@ Format: [`reference.md`](reference.md) → "Recap".
**never** worktrees — the `ship_*` flow + post-merge cleanup handle those.
- Skip missing / non-git / detached-HEAD repos with a one-line note.
- Never skip hooks, never force-push — these are read/prune/delete operations only.
- Suggest `/worktree_status` first if unsure whether tasks are in flight.
- Suggest `/health worktrees` first if unsure whether tasks are in flight.
- Execution-environment fallback (remote-audit-only when there's no local tree)
is in [`reference.md`](reference.md).
2 changes: 1 addition & 1 deletion skills/repo_cleanup/reference.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ prune candidates (`git remote prune --dry-run origin`).

## Audit worktrees

Reuse `worktree_status` logic (don't duplicate it) to get: every real worktree
Reuse the `/health worktrees` procedure logic (don't duplicate it) to get: every real worktree
under `$PYAUTO_WT_ROOT/<task>/<repo>`; which task each belongs to per `active.md`;
orphan roots; missing roots; dirty/unpushed counts. Collect the set of
`(repo, branch)` pairs checked out in any worktree — **protected**, excluded from
Expand Down