Trigger Phrases
Say any of these to activate this skill:
"generate standup""auto standup""standup summary""what did the team do""morning summary""daily summary"
Tools Used
search_integrations connect memory_read write_file send_message
How It Works
Auto-generate standup summaries from development activity:
- Connect — Slack via Composio if the user wants Slack context. GitHub always via
gh:exec({ command: "gh auth status" })(saveGITHUB_TOKENto.envif needed)connect({ name: "slack" })if not connected (optional but recommended)
- Gather data — Pull last 24h of activity:
- GitHub:
gh pr list,gh issue list,gh api .../commitsper developer - Slack (if connected): messages in engineering channels for context
- GitHub:
- Classify — For each team member, categorize activity into:
- Done: merged PRs, closed issues, significant commits
- In Progress: open PRs, branches with recent commits
- Blockers: PRs with requested changes, stale PRs (>2 days no review), failing CI
- Generate summary — Build structured standup:
**Daily Standup — {date}** **{Developer Name}** Done: Merged PR #123 (feature X), closed issue #456 In Progress: PR #789 (refactor Y) — awaiting review Blockers: None **{Developer Name 2}** ... - Build canvas — Update standup dashboard:
- Today’s summary with per-person sections
- KPIs: team members active, PRs in flight, commits yesterday
- Blockers section highlighted at top
- Deliver — Post compiled summary to configured Slack channel
- Archive — Save to memory for historical reference and pattern detection
- Track recurring blockers across standups
- Flag developers with no activity (may be on PTO or blocked)