Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From standup-autopilot
Render today's standup card from what your agents actually did across repos
How this skill is triggered — by the user, by Claude, or both
Slash command
/standup-autopilot:standupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
!`node "${CLAUDE_SKILL_DIR}/../../standup-autopilot.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/standup-autopilot.js" --render`
!node "${CLAUDE_SKILL_DIR}/../../standup-autopilot.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/standup-autopilot.js" --render
The card above is your standup for the most recent day with recorded sessions —
one line per repo (what got done, tests run, PRs, diffstat) plus any unresolved
blockers. It is produced by the standup-autopilot hook, which snapshots each
session's outcome (task, git state, tests, PRs, blockers) to a local per-day
ledger as you work.
Briefly restate it as a ready-to-paste standup: a short "Yesterday" line per repo and a "Blocked on" list (or note there are no blockers). Keep it tight; do not re-run any commands.
npx claudepluginhub karanb192/claude-code-hooks --plugin standup-autopilotCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.