/ca-standup — daily hygiene
The best-practice checklist you run when you sit down to code, made routine and
gated. The SessionStart briefing reports hygiene state read-only; this command is
where the actions happen — each one confirmed individually, none taken unbidden.
Arbiter gathers and proposes; you decide every mutation.
Flow
The orchestrator reads the current repo state (reusing the briefing's read-only
computation — branch, ahead/behind, dirty tree, stashes, prune-candidate branches,
stale worktrees) and presents it, then offers each applicable action in turn. Skip
an action that has no candidates; never bundle confirmations.
- Fetch + fast-forward pull — kick
git fetch, then offer a --ff-only
pull of the current branch. Eligibility is the briefing summary's
ff_pull_eligible flag (SH-6: clean working tree AND behind upstream) — the same
pure helper the SessionStart briefing computes, not a condition re-derived here.
On a dirty tree the pull is withheld and the dirty state is reported instead. A
diverged branch (would need a merge) is refused with a diverged-branch message —
never a merge commit.
- Prune merged local branches — list local branches already merged on remote
(the
: gone] upstream set), excluding the current branch and the default
(main). Delete a listed branch only after an explicit per-branch confirmation;
declining leaves it in place.
- Remove stale worktrees — list stale/merged worktrees (branch gone-or-merged,
or path missing on disk), never the main worktree. Remove one only after explicit
per-item confirmation; declining leaves it intact.
- Surface stashes / dirty / un-pushed — list stashes, uncommitted changes, and
un-pushed commits, each with a suggested next step (
/ca-commit, git push,
git stash show). Report-and-route only: never discard a stash, reset, or push.
- Advisory board-drift sweep — run
git log over the recent merge window
(since the last ca-scoped tag, or a rolling 30-day window when no tag exists)
and pipe that text to
python3 "<plugin-root>/hooks/boardsync.py" reconcile || python "<plugin-root>/hooks/boardsync.py" reconcile.
Display the advisory drift report as-is: DRIFTED tasks (work merged but board
state not [x]) and informational UNKNOWN ids (in the log but absent from the
board). This step is read-only and best-effort — the dotted-id grep can miss a
task never named in a commit. The board is never mutated here; open-tasks.md
is never written. Any drifted task must be resolved explicitly through
/ca-task done <id> — the only blessed board writer. State this clearly to the
user; do not auto-flip.
Present a one-line summary of what was done and what was declined.
When NOT to use
- A read-only state snapshot without acting →
/ca-status.
- Install health (interpreter, payload, hooks) →
/ca-doctor.
- Committing staged work →
/ca-commit.
Hard gate
- MUST pull with
--ff-only and ONLY on a clean working tree — never a merge
commit, never on a dirty tree, never a rebase.
- MUST exclude the current branch and the default branch from branch pruning, and
the main worktree from worktree cleanup.
- MUST confirm each destructive action (branch delete, worktree remove)
individually before performing it — no batched or implied yes.
- MUST treat stash / dirty / un-pushed state as report-and-route only — never
discard, reset, force, or push on the user's behalf.
- MUST NOT write to or force-push the default branch.
- MUST NOT auto-flip any board entry during the drift sweep — the sweep is advisory
and read-only; resolving a drifted task is the user's decision and routes
exclusively through
/ca-task done <id>.
1---2name: ca-standup-23description: Daily repo hygiene — review the day's repo state, then perform the cleanups under per-action confirmation. Fast-forward only, never destructive without a yes.4---56# /ca-standup — daily hygiene78The best-practice checklist you run when you sit down to code, made routine and9gated. The SessionStart briefing *reports* hygiene state read-only; this command is10where the *actions* happen — each one confirmed individually, none taken unbidden.11Arbiter gathers and proposes; you decide every mutation.1213## Flow1415The orchestrator reads the current repo state (reusing the briefing's read-only16computation — branch, ahead/behind, dirty tree, stashes, prune-candidate branches,17stale worktrees) and presents it, then offers each applicable action in turn. Skip18an action that has no candidates; never bundle confirmations.19201. **Fetch + fast-forward pull** — kick `git fetch`, then offer a **`--ff-only`**21 pull of the current branch. Eligibility is the briefing summary's22 `ff_pull_eligible` flag (SH-6: clean working tree AND behind upstream) — the same23 pure helper the SessionStart briefing computes, not a condition re-derived here.24 On a dirty tree the pull is withheld and the dirty state is reported instead. A25 diverged branch (would need a merge) is refused with a diverged-branch message —26 never a merge commit.272. **Prune merged local branches** — list local branches already merged on remote28 (the `: gone]` upstream set), excluding the current branch and the default29 (`main`). Delete a listed branch only after an explicit per-branch confirmation;30 declining leaves it in place.313. **Remove stale worktrees** — list stale/merged worktrees (branch gone-or-merged,32 or path missing on disk), never the main worktree. Remove one only after explicit33 per-item confirmation; declining leaves it intact.344. **Surface stashes / dirty / un-pushed** — list stashes, uncommitted changes, and35 un-pushed commits, each with a suggested next step (`/ca-commit`, `git push`,36 `git stash show`). Report-and-route only: never discard a stash, reset, or push.375. **Advisory board-drift sweep** — run `git log` over the recent merge window38 (since the last `ca`-scoped tag, or a rolling 30-day window when no tag exists)39 and pipe that text to40 `python3 "<plugin-root>/hooks/boardsync.py" reconcile || python "<plugin-root>/hooks/boardsync.py" reconcile`.41 Display the advisory drift report as-is: DRIFTED tasks (work merged but board42 state not `[x]`) and informational UNKNOWN ids (in the log but absent from the43 board). This step is read-only and best-effort — the dotted-id grep can miss a44 task never named in a commit. The board is never mutated here; `open-tasks.md`45 is never written. Any drifted task must be resolved explicitly through46 `/ca-task done <id>` — the only blessed board writer. State this clearly to the47 user; do not auto-flip.4849Present a one-line summary of what was done and what was declined.5051## When NOT to use5253- A read-only state snapshot without acting → `/ca-status`.54- Install health (interpreter, payload, hooks) → `/ca-doctor`.55- Committing staged work → `/ca-commit`.5657## Hard gate5859- MUST pull with `--ff-only` and ONLY on a clean working tree — never a merge60 commit, never on a dirty tree, never a rebase.61- MUST exclude the current branch and the default branch from branch pruning, and62 the main worktree from worktree cleanup.63- MUST confirm each destructive action (branch delete, worktree remove)64 individually before performing it — no batched or implied yes.65- MUST treat stash / dirty / un-pushed state as report-and-route only — never66 discard, reset, force, or push on the user's behalf.67- MUST NOT write to or force-push the default branch.68- MUST NOT auto-flip any board entry during the drift sweep — the sweep is advisory69 and read-only; resolving a drifted task is the user's decision and routes70 exclusively through `/ca-task done <id>`.