agents/skills/standup/SKILL.md
Generate a daily standup summary from recent git activity, commits, open PRs, and current work in progress. Use for daily standup prep or summarizing recent work.
npx skillsauth add drn/dots standupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate a quick summary of recent work for standups or status updates.
$ARGUMENTS - Optional: --team to include all authors, or a custom time range (e.g., "3 days")git branch --show-currentgit config user.email 2>/dev/null | head -1git config user.name 2>/dev/null | head -1git log --all --oneline --since="yesterday" 2>/dev/null | head -30gh pr list --author @me --state open 2>/dev/null | head -20git status --short 2>/dev/null | head -10git branch --sort=-committerdate --format='%(refname:short) %(committerdate:relative)' 2>/dev/null | head -10--team is in $ARGUMENTS, include all authors. Otherwise filter to the current user (match against the git user email and name from context).Run git log filtered to the appropriate author and time range:
git log --all --oneline --author="<email>" --since="<range>"
Also check for any PRs merged in the time range:
gh pr list --author @me --state merged --limit 10
Print in this format:
## Standup — <date>
### Yesterday
- <commit summary grouped by branch/feature>
- <PRs merged>
### Today
- <inferred from current branch name and uncommitted changes>
- <open PRs that need attention>
### Open PRs
- #<number>: <title> (<status/checks>)
If there is no activity for "Yesterday", say "No commits found" rather than omitting the section.
For "Today", infer from:
After presenting the standup, offer to:
pbcopy)development
Walk every unresolved review thread on a PR, triage each one, reply with a rationale of whether or not the comment will be acted upon, make the code change if warranted, and mark the thread resolved. Use when the user asks to address only the open PR comments without re-running CI, respond to review feedback, resolve review threads, or clear bot comments on a PR.
tools
Iteratively run /rereview, fix the findings, and loop until reviewers approve clean. Use for iterative automated review, when you want /rereview to loop until clean, or for a paranoid pre-merge review that auto-addresses every blocker.
development
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.
development
Create reviewed Codex goal setup packages for long-running /goal work. Use when the user wants to turn an idea, backlog, project mission, or vague objective into durable goal files under a project goals slug folder, with Plannotator review gates for brief, narrative plan with acceptance criteria, verification, blockers, and the final /goal prompt.