standup · karanb192 — Claude Code skill: what it does and how to install
Builds a standup card from agent sessions across repositories. It uses the latest day with recorded sessions, which may not be today.
MIT ★ 586 updated 2026-10-26
/plugin marketplace add karanb192/claude-code-hooks
/plugin install standup-autopilot@claude-code-hooksWhat standup does
The standup-autopilot hook saves each session’s outcome to a local daily ledger, including the task, Git state, tests, PRs, and blockers. The skill renders a card for the latest day with recorded sessions. Each repository gets a line with completed work, tests run, PR details, and diff stats; unresolved blockers appear as well.
The result is meant to be restated as a short, ready-to-paste update: one “Yesterday” line per repository, followed by a “Blocked on” list or a note that there are no blockers. It does not rerun commands. Automatic model invocation is disabled, so call it explicitly with /standup. The reporting date follows the session records, so a card may cover an earlier day.
What it helps with
- summarize agent work across repositories
- show tests run and related PRs
- surface unresolved session blockers
- draft repository-by-repository standup updates
Example prompts for the agent
- Create a standup from the latest recorded sessions with
/standup. - Summarize agent work for each repository and list blockers using
/standup. - Draft concise “Yesterday” lines for my standup with
/standup.
How to install standup
1Plugin marketplace
/plugin marketplace add karanb192/claude-code-hooks/plugin install standup-autopilot@claude-code-hooksThis installs the whole standup-autopilot plugin with all its skills
2Skills CLI (Vercel)
npx skills add karanb192/claude-code-hooks --skill standup -a claude-code3Manually: put the files in place
~/.claude/skills/standup/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/standup/
1Skills CLI (Vercel)
npx skills add karanb192/claude-code-hooks --skill standup -a codex2Manually: put the files in place
.agents/skills/standup/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add karanb192/claude-code-hooks --skill standup -a cursor2Manually: put the files in place
.cursor/skills/standup/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install karanb192/claude-code-hooks plugins/standup-autopilot/skills/standup2Manually: put the files in place
.github/skills/standup/SKILL.md1Skills CLI (Vercel)
npx skills add karanb192/claude-code-hooks --skill standup -a gemini-cli2Platform CLI
gemini skills install https://github.com/karanb192/claude-code-hooks --path plugins/standup-autopilot/skills/standupManually: put the files in place
.devin/skills/standup/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about standup
How do I install standup in Claude Code?
Add the marketplace with /plugin marketplace add karanb192/claude-code-hooks, then install the plugin with /plugin install standup-autopilot@claude-code-hooks.
What does the standup skill do?
It turns recent agent session records into a repository-by-repository card with work completed, tests, PR details, diff stats, and blockers.
What information does the standup card include?
The daily ledger records each session’s task, Git state, tests, PRs, and blockers. The rendered card also reports work and diff stats for each repository.
Source text
SKILL.md · MIT
---
name: standup
description: Render today's standup card from what your agents actually did across repos
disable-model-invocation: true
---
# Standup card
!`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.
© Karan Bansal · MIT · karanb192/claude-code-hooks
Similar skills
All skills for Notes, tasks and projects →standup by other authors comes first.