
Writes your daily standup from your Claude Code sessions: tasks, tests, PRs and blockers per repo, kept on your machine.
by karanb192· Project managementUnclaimed · Yours? Claim it
4 images
About
Standup Autopilot is a Claude Code plugin by Karan Bansal, part of his claude-code-hooks collection. It's a community project. It writes your daily standup from what your coding sessions actually did, read from Claude Code's own session transcripts rather than from commits or tickets, and brings yesterday's unresolved blockers back into your next session. What it does - Each time a session stops or ends, it reads that session's transcript and saves a snapshot to a local ledger for the day: a one-line summary of the task, the git branch and uncommitted diffstat, the test commands that ran with their pass or fail results, PR numbers mentioned in the session, and blockers (tool errors that were never resolved, and failing tests). - When you start Claude Code, it adds the previous day's open blockers to the agent's context. On the first session of the day it also prints a standup card in the terminal. - /standup-autopilot:standup shows the card for your last working day: one line per repo with what got done, tests, PRs and diffstat, plus anything you're blocked on. The agent then restates it as a ready-to-paste "Yesterday" and "Blocked on" update. What it reads - Your local Claude Code session transcripts. - Each repo's current git branch and git diff --shortstat, run locally. - It doesn't connect to GitHub, Linear, Jira or Slack. PRs come only from pull-request links or "PR #123" mentions in the session. How to install In Claude Code, run /plugin marketplace add karanb192/claude-code-hooks, then /plugin install standup-autopilot@claude-code-hooks, and restart Claude Code. The hooks run with Node.js. There's nothing to configure. Good to know - Everything stays on your machine; the plugin makes no network calls. Ledgers are kept in ~/.claude/standup/ (one file per day) and hook logs in ~/.claude/hooks-logs/. - Token-shaped strings (GitHub, Slack and sk- keys, AWS keys, JWTs, key=value secrets) are redacted before anything is written to disk. - "Yesterday" is the most recent earlier day with recorded sessions, so a Monday standup picks up Friday's work. - The same marketplace has more hooks from Karan Bansal, such as guards against dangerous commands and secret leaks.
Once it’s added
“/standup-autopilot:standup”
“Turn yesterday's standup card into an update I can paste into Slack.”
“What was I blocked on yesterday, and can we pick that up first?”
“Which repos did I work in yesterday, and did the tests pass?”
Before you add it
Reads only
Your local Claude Code session transcripts · Each repo's git branch and uncommitted diffstat
Makes changes · your agent can ask first
A per-day standup ledger in ~/.claude/standup/ · Yesterday's open blockers into your next session's context
From people who use it
Step by step
Nothing new reaches your agent until a person has looked at it.
Plugins people install alongside Standup Autopilot.
No reviews yet. Used Standup Autopilot? Say how it went.
Write a reviewRuns on your machine.
Runs on your machine.
/plugin marketplace add karanb192/claude-code-hooks /plugin install standup-autopilot@claude-code-hooks
Scanned and passed · checked 6 h ago
Plugins people install alongside Standup Autopilot.
A GitHub issue resolver, a standup-notes command and a developer-experience subagent, for teams working with a coding agent.
A community skill that has your agent write INVEST user stories with acceptance criteria, split epics and plan sprints from your velocity.
Product management skills and commands for your agent: PRDs, OKRs, roadmaps, sprint plans, retros, pre-mortems, user stories and more.
Nobody has shared how they use Standup Autopilot yet.
Scanned on every change, and again when our rules improve.
Tell us and a person on the trust team will look at it. Or email [email protected].
Security scan
Passed
Safe to install in every agent it supports. Claude plugins.