standup-reporter

Convert commits, pull requests, and ticket updates into standup updates.

2|1|Updated May 17, 2026

Search Tags:#blockers #team communication #status update #standup #commit summary

Ready to run

npx skills add https://github.com/rakibulism/agent-skills-os --skill standup-reporter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: standup-reporter
Source: https://github.com/rakibulism/agent-skills-os/tree/main/skills/standup-reporter
Command: npx skills add https://github.com/rakibulism/agent-skills-os --skill standup-reporter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns raw work activity into a concise, teammate-friendly standup update so you can communicate progress without manually rewriting commits, PRs, or ticket notes.

Core Features & Use Cases

Outcome-focused summaries: Groups related work by result instead of listing every commit or task.
Standup-ready formatting: Produces a clear Yesterday / Today / Blockers structure that is easy to share in meetings or async updates.
Blocker and FYI surfacing: Highlights dependencies, risks, and decisions that teammates should know about.
Use case: Paste in a few commit messages, PR titles, and ticket updates, and get back a polished standup note that explains what changed, what is next, and what is blocking progress.

Quick Start

Turn this recent activity into a concise standup update with Yesterday, Today, Blockers, and FYI sections.

Frequently Asked Questions about standup-reporter

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

FAQPage Schema

How do I generate a daily standup update from commit messages and pull requests?▼

To generate a daily standup update from commit messages and pull requests, paste your recent engineering activity into the Skill. It converts raw commits, PR titles, and ticket notes into a concise Yesterday / Today / Blockers format.

What is the best way to format async status updates for team communication?▼

The best way to format async status updates for team communication is to group related work by outcome rather than listing every commit. This Skill produces a teammate-friendly summary highlighting near-term plans, dependencies, and explicit blockers.

Can I turn rough engineering notes into a structured standup report?▼

Yes, you can turn rough engineering notes into a structured standup report. The Skill processes rough notes from ticket updates and pull requests, applying outcome-oriented summarization to extract what changed, what is next, and what is blocking progress.

Does the standup summary include FYI and blocker context for teammates?▼

Yes, the standup summary includes FYI and blocker context for teammates. It surfaces dependencies, risks, and decisions that teammates should know about, ensuring the daily status update communicates progress with explicit blockers and teammate-relevant context.

What is the structure of the standup update generated from recent engineering activity?▼

The structure of the standup update generated from recent engineering activity follows a clear Yesterday, Today, Blockers, and FYI format. This standup-ready formatting is designed to be easy to share in meetings or async team communication posts.