Menu
Use when the user asks for a standup update, daily summary, "what did I work on yesterday", or wants to recap recent commits before a team sync.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when preparing notes for a 1:1 with a report, drafting written feedback, or summarizing a person's recent work/contributions ahead of a conversation or review cycle.
Use when asked to generate or update architecture diagrams or ER (entity-relationship) diagrams from the codebase — the code is the source of truth, not existing docs.
Use when the user asks how to reduce Claude Code costs, manage token usage, choose the right model for a task, or wants a review of whether a session/workflow is running efficiently.
Use when investigating a bug, test failure, or unexpected behavior and proposing a fix — always runs investigation in Plan Mode so no code changes happen until the root cause and approach are confirmed.
Use when writing or reviewing code that crosses a trust boundary (user input, external APIs, file/network/DB I/O) — guards against invalid input, injection, unsafe failure modes, and missing validation at the edges without over-defending internal code.
Use when reviewing local code changes for correctness and assessing the blast radius / impact of a change — what else could break, who/what depends on the changed code.
| name | daily-standup |
| description | Use when the user asks for a standup update, daily summary, "what did I work on yesterday", or wants to recap recent commits before a team sync. |
Produces a concise standup update (yesterday / today / blockers) from local git activity.
Find the relevant time window. Default to "since yesterday at this time":
git log --all --author="$(git config user.name)" --since="yesterday" --oneline --no-merges
If that's empty, widen to --since="3 days ago" and say so.
For each commit, look at git show --stat <hash> only if the one-line summary
is unclear — don't dump full diffs into the update.
Check for in-flight work: git status --short and git diff --stat.
Draft the update in this format:
**Yesterday:** <2-4 bullet points summarizing merged/completed work, in plain language>
**Today:** <inferred from uncommitted/in-progress work, or ask the user if unclear>
**Blockers:** <ask the user — don't invent blockers>
Keep it to what a teammate would actually want to hear — group related commits, skip "fix typo" noise, translate commit-speak into outcomes ("shipped X" not "feat: x").