standup
Daily standup from git history and GitHub activity: what changed since yesterday, what's in flight, what's blocked.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-19
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- standup
- effort
- low
- description
- Daily standup from git history and GitHub activity: what changed since yesterday, what's in flight, what's blocked.
- allowed-tools
- Bash(git log*), Bash(git config*), Bash(gh pr*), Bash(gh issue*), Read
02 资源文件 1
- 参考文档agents/openai.yaml145 B
03 SKILL.md 正文
Standup
One person's report: what changed since yesterday, what's in flight, and what's blocked. Shared ownership, handoffs, dependency collisions, and merge coordination across several agents or operators belong to the agent-standup skill instead.
1. Gather activity
git log --since="1 day ago" --oneline --author="$(git config user.email)"
gh pr list --author="@me" --state=open
gh issue list --assignee="@me" --state=open
The window is always the last 24 hours (--since="1 day ago"), taken from
git and GitHub timestamps rather than estimated, so every day's report covers
the same span. Only commits under
your git email and issues assigned to you show up; when a section comes back
empty, say so rather than filling it from memory.
Done when you have yesterday's commits, your open PRs, and your assigned issues.
2. Write the report
## Standup — [Date]
### Yesterday
- [type]: [one-liner per commit/PR]
### Today
- [planned task from open issues/PRs]
### Blockers
- [none | what's blocking]
Infer "Today" from the open PRs and issues. Report blockers, unfinished tasks, and dependencies plainly: a hidden blocker is one nobody can help with.
Done when every section has an entry, with "none" under Blockers when nothing blocks.
Related
agent-standup— reconcile multi-agent and multi-operator work.
04 同仓库更多 Skills
teach
Teach yourself a topic over several sessions, with lessons, references, and a record of what you've learned.
svg-logo-designer
Generate SVG logos with multiple concepts, layouts, and color variations.
documentation-writer
Writes and revises human-facing documentation — READMEs, contributor and setup guides, reference pages, architecture notes, CLAUDE.md, and changelog entries. Covers picking the right document type for the question being asked, structuring for skimming, writing examples that actually run, and keeping docs from going stale. Use when creating or rewriting docs, when a README has drifted from the code, or when deciding where a piece of information belongs. For SKILL.md and agent files, use /skill-writer instead.
adhd-mode
Shapes every response for a reader with ADHD: the next action first, numbered steps, progress restated each turn, tangents held back, concrete time estimates, wins made visible. Stays on for the rest of the session until the reader says "stop adhd mode". On Claude Code, the harness-kit:adhd output style does the same without invoking this skill.
wait-what
That last message didn't land: re-explain it with the missing context.
to-questionnaire
Turn a decision you can't make alone into a questionnaire for the one person who can answer it, filled in async or together in a meeting.