Agent skill
ai-standup
Use when preparing daily standup notes or summarizing recent PR and commit activity for team updates.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/ai-standup-arcasilesgroup-ai-engineering
SKILL.md
Standup
Purpose
Generate standup notes from actual PR and commit activity. Produces concise, copy-paste-ready summaries grouped by status. Eliminates manual standup preparation.
Trigger
- Command:
/ai-standup - Context: preparing for daily standup, team sync, or async status update.
When to Use
- Before daily standup meetings
- Async status updates for Slack/Teams channels
- End-of-day summaries
- Handoff notes between sessions
When NOT to Use
- Sprint-level summaries -- use
/ai-sprint retro - Incident timelines -- use
/ai-postmortem
Pre-conditions (MANDATORY)
- Read
.ai-engineering/manifest.yml—work_itemssection. - Use the active provider to gather work item data:
- GitHub:
gh issue list --label <team_label> --state all --json ... - Azure DevOps:
az boards query --wiql "..."filtered byarea_pathand current iteration
- GitHub:
- Include work item status in standup notes when available.
Procedure
-
Determine lookback -- default: 1 working day. Override with
--days N. Skip weekends unless--daysexplicitly covers them. -
Collect activity -- scan the following sources: a.
git log --since="N days ago" --author="<name>"-- local commits b.gh pr list --author="<name>" --state=all --json title,url,state,updatedAt-- PRs c. Active spec tasks from.ai-engineering/specs/spec.mdandspecs/plan.md-- current work -
Classify items into three groups:
Group Criteria Shipped Merged PRs, completed spec tasks In Progress Open PRs, branches with recent commits, active spec tasks Blocked PRs with review requests pending 24h+, tasks marked blocked -
Format output -- markdown to stdout:
## Standup — YYYY-MM-DD
### Shipped
- Merged PR #123: Add secret scanning to commit hook [link]
- spec-054: Task 2.1 -- hook installation complete
### In Progress
- PR #125: Telemetry event schema (awaiting review) [link]
- spec-054: Task 3.2 -- guard event integration
### Blocked
- PR #120: Dependency update blocked on upstream release
- Author resolution -- if
--authornot specified, detect fromgit config user.nameorgh api user.
Arguments
| Argument | Default | Description |
|---|---|---|
--days N |
1 | Lookback period in working days |
--author <name> |
current user | Filter by author name or GitHub handle |
Quick Reference
/ai-standup # today's standup
/ai-standup --days 3 # last 3 days (covers a long weekend)
/ai-standup --author @alice # standup for a specific team member
Output
- Markdown to stdout (not saved to file)
- Designed for copy-paste into Slack, Teams, or standup tools
- Each item includes a link when available
$ARGUMENTS
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?