Daily Standup Summarizer
Collect GitHub activity and generate standup summaries for the team
Prerequisites
- OpenClaw installed and running
- GitHub organization or repos to monitor
- Slack workspace with a standup channel
Required Skills
openclaw install github-auto-propenclaw install slack-digestopenclaw install commit-analyzerInstallation Steps
Install required skills
Install the GitHub, Slack, and commit analysis skills.
openclaw install github-auto-pr slack-digest commit-analyzerConfigure team members
List the GitHub usernames of your team members and the number of lookback days for activity collection.
Add the config snippet
Copy the configuration below and replace the team member names and Slack channel.
Configuration
{
"schedules": [
{
"name": "standup-summary",
"cron": "0 9 * * 1-5",
"actions": [
"collect-github-activity",
"analyze-commits",
"summarize-prs",
"post-standup"
]
}
],
"standup": {
"teamMembers": ["alice", "bob", "charlie"],
"lookbackDays": 1,
"includeStats": true
}
}Add this to your openclaw.json and customize the values for your setup.
SOUL.md
## Standup Summary Guidelines
- Keep each person's section to 2-3 bullet points max. Summarize themes, don't list every commit.
- Highlight blockers and stalled PRs prominently at the top — these are what the team needs to act on.
- If someone had no activity, say "No GitHub activity yesterday" rather than omitting them. Visibility matters.
- Group related commits into themes: "Worked on auth refactor (4 commits)" not a list of 4 commit messages.
- Flag PRs that have been open for 3+ days without review — these are falling through the cracks.
- Tone should be neutral and factual. This isn't a performance report — it's a coordination tool.Add this to your SOUL.md to define the agent's behavior for this workflow.
Expected Behavior
Every weekday morning at 9am, OpenClaw collects yesterday's GitHub activity (commits, PRs, reviews) for each team member, generates a summary, and posts it to Slack as a standup digest.
Usage Guide
The standup runs on weekdays automatically. Each team member's activity is summarized with commits, PRs opened/merged, and reviews completed. Add or remove team members by editing the teamMembers array.
More DevOps Recipes
All Recipes →Sentry → Auto-Debug → Open PR
Automatically analyze Sentry errors, generate fixes, and create pull requests
PR Review Automation
Automatically review pull requests with security scanning and style checks
Incident Response Automation
Detect production issues and coordinate incident response