standup

Generate daily standup summaries from GitHub PR activity.

9|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/gewoonseba/dotfiles --skill standup-gewoonseba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: standup
Source: https://github.com/gewoonseba/dotfiles/tree/main/claude/.claude/skills/standup
Command: npx skills add https://github.com/gewoonseba/dotfiles --skill standup-gewoonseba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly convert GitHub PR activity into a clear daily standup summary, saving time on meeting prep and note-taking.

Core Features & Use Cases

  • Automates the creation of a standup summary from yesterday's merged PRs.
  • Open PR visibility: lists open PRs and their statuses (Draft, In Review, Approved).
  • Standup continuity: checks for existing standup entries for the target date and updates them if needed.
  • Saving outputs to your Standup notes file for easy access and archival.

Quick Start

Use the standup skill to generate yesterday's standup notes for a specific standup date and save them to your notes file.

Frequently Asked Questions about standup

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

FAQPage Schema
How do I generate a daily standup summary from GitHub PR activity?

To generate a daily standup summary from GitHub PR activity, you need a standup date input, which automatically aggregates merged PRs from the previous day. It categorizes open PRs by draft status and review decision, formatting everything into prescribed standup sections.

What is the best way to automate standup notes from merged GitHub PRs?

Automating standup notes from merged GitHub PRs is done by applying a standup date to fetch the prior day's PR activity. The tool aggregates merged pull requests, categorizes open ones by review state, and saves the formatted output to your standup notes file.

Can I use GitHub PR review status to prepare retrospective meeting notes?

Yes, you can use GitHub PR review status to prepare retrospective meeting notes by summarizing the previous day's PR activity. The categorization of open PRs by isDraft and reviewDecision provides clear visibility into your code review pipeline.

Does this standup automation tool check for existing notes on the target date?

Yes, this standup automation tool checks for existing standup entries for the target date. It provides standup continuity by verifying if notes already exist and updates them if needed before saving the aggregated PR activity summary.

How are open pull requests categorized in the generated standup output?

Open pull requests are categorized in the generated standup output by their isDraft status and reviewDecision. This categorization organizes open PRs into clear statuses like Draft, In Review, or Approved for better meeting visibility.

What limitations exist when automating daily standup summaries from pull request data?

A limitation when automating daily standup summaries from pull request data is that the PR activity date is fixed to exactly one day before the provided standup date, meaning it cannot summarize custom multi-day or real-time PR activity ranges.