standup-auto-generate

Generate structured standup summaries from GitHub activity and Slack messages.

12|6|Updated Dec 2, 2025

Search Tags:#github #agile #slack #standup #daily #team-productivity #standup-generator

Ready to run

npx skills add https://github.com/shogo-labs/shogo-ai --skill standup-auto-generate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: standup-auto-generate
Source: https://github.com/shogo-labs/shogo-ai/tree/main/packages/agent-runtime/templates/project-manager/.shogo/skills/standup-auto-generate
Command: npx skills add https://github.com/shogo-labs/shogo-ai --skill standup-auto-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual standups are time-consuming and prone to miscommunication, causing teams to miss important updates.

Core Features & Use Cases

Gather GitHub activity (commits, PRs) and Slack messages from the last 24 hours
Produce per-person status sections with Done, In Progress, and Blockers
Build a standup canvas/dashboard and post the summary to Slack; archive for future reference

Quick Start

Generate today's standup summary from the latest GitHub activity and Slack messages.

Frequently Asked Questions about standup-auto-generate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate daily standup summaries from GitHub and Slack activity?▼

Automate daily standup summaries by connecting GitHub and Slack to analyze the last 24 hours of commits, PRs, and messages, grouping contributions into Done, In Progress, and Blockers sections per contributor.

Can I generate per-person engineering updates without manual input?▼

Generate per-person engineering updates by analyzing GitHub commits and Slack messages from the past 24 hours, automatically categorizing activity into structured Done, In Progress, and Blockers sections for each team contributor.

Does generating standups from GitHub and Slack require specific environment setup?▼

Generating automated standups requires connected GitHub and Slack environments to access the last 24 hours of commits, pull requests, and team messages needed to build the per-person status dashboard.

What is the best way to share automated agile standups with a team?▼

Share automated agile standups by building a standup canvas dashboard from GitHub and Slack activity and posting the structured summary directly to Slack, while archiving it for historical team productivity trends.

How does automated standup generation handle blockers from team conversations?▼

Automated standup generation handles blockers by analyzing the last 24 hours of Slack messages and GitHub activity, identifying and extracting conversation details to categorize them into a dedicated Blockers section for each contributor.

Are automated standup summaries archived for historical tracking?▼

Automated standup summaries are archived after being posted to Slack, enabling engineering teams to track historical trends and review past daily updates, work done, and blockers over time.