standup-summary

Generates daily standup summaries from git commit history and GitHub issues.

3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/jholhewres/devclaw-skills --skill standup-summary-jholhewres
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: standup-summary
Source: https://github.com/jholhewres/devclaw-skills/tree/main/skills/standup-summary
Command: npx skills add https://github.com/jholhewres/devclaw-skills --skill standup-summary-jholhewres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of daily standup summaries by consolidating information from your version control system and issue tracker, saving you time and ensuring consistent reporting.

Core Features & Use Cases

  • Yesterday's Activity: Gathers commits, merged PRs, and closed issues from the past 24 hours.
  • In-Progress Tracking: Identifies issues currently marked as "in-progress".
  • Structured Output: Organizes information into "Done", "In Progress", and "Blocked" sections.
  • Use Case: Automatically generate your team's daily standup report to post in Slack, ensuring everyone is aware of progress and potential roadblocks.

Quick Start

Use the standup-summary skill to generate a report of your team's activity from yesterday.

Frequently Asked Questions about standup-summary

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

FAQPage Schema
How do I generate a daily standup summary from git commits and GitHub issues?

Generate a daily standup summary by using bash scripting with git and gh CLI to collect and format activity data. The tool analyzes your commit history and issues to track completed tasks, ongoing work, and blockers.

Does the standup summary automation work with GitHub issues and git history?

Yes, the standup summary automation works with GitHub issues and git history by leveraging the gh CLI and git commands. It gathers commits, merged PRs, and closed issues from the past 24 hours to build the report.

What is the best way to track yesterday's git activity for an agile team report?

The best way to track yesterday's git activity is to automate data collection using bash scripting. This approach gathers your merged PRs and closed issues from the past 24 hours and organizes them into structured standup sections.

How to format standup reports into Done, In Progress, and Blocked sections?

Format standup reports into Done, In Progress, and Blocked sections by running a bash script that scopes your git commit history and GitHub issues. This structured output ensures consistent reporting for agile development teams.

Can I use this tool to identify blockers and in-progress GitHub issues for standups?

Yes, you can identify blockers and in-progress GitHub issues for standups. The script specifically scopes to tracking ongoing work by finding issues currently marked as in-progress and organizing them into a dedicated Blocked section.

Do I need the gh CLI installed to automate standup summaries from version control?

Yes, you need the gh CLI installed to automate standup summaries from version control. The skill leverages bash scripting alongside git and gh CLI tools to collect and format the necessary activity data from your repositories.