ca-standup
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.
npx skills add arbiterForge/codeArbiter --skill ca-standup --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# $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 across different actions or items — branch deletions always stay per-item, and the sole exception is step 3's explicitly enumerated worktree group, which is still one confirmation that names every member, never an implied yes. 1. **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 tr
- Flow
- When NOT to use
- Hard gate
What does the ca-standup skill do?
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.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill ca-standup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From arbiterForge/codeArbiter, a repository with 138 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.