Standup Skill

Aggregate developer activity logs and GitHub pull request data into a daily standup report.

3|Updated Nov 19, 2025

Search Tags:#workflow automation #daily report #developer productivity #github integration #standup #activity summary

Ready to run

npx skills add https://github.com/meaganewaller/.dotfiles --skill standup-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Standup Skill
Source: https://github.com/meaganewaller/.dotfiles/tree/main/home/.claude/skills/common/standup
Command: npx skills add https://github.com/meaganewaller/.dotfiles --skill standup-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This skill automates the generation of your daily standup report by aggregating your recent activity, helping you quickly summarize your work for your team.

Core Features & Use Cases

Activity Aggregation: Gathers data from dev-os events, session durations, and GitHub activity.
Structured Output: Presents a clear, organized standup report in a standard markdown format.
Use Case: At the start of your workday, invoke this skill to get a summary of what you accomplished yesterday and what your priorities should be for today.

Quick Start

Run the standup skill to generate your daily report.

Frequently Asked Questions about Standup Skill

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

FAQPage Schema

How do I generate a daily standup report from GitHub activity?▼

To generate a daily standup report, this skill aggregates your developer event logs and GitHub pull request data to summarize completed tasks, sessions, and pending items from the previous day into a structured markdown format.

Do I need the GitHub CLI to automate my daily standup report?▼

The GitHub CLI is an optional dependency used to fetch pull request information for your daily standup report, while the core activity aggregation relies primarily on accessing your local dev-os event logs.

What is the best way to summarize developer activity for a standup?▼

Summarizing developer activity for a standup is best handled by aggregating event logs, session durations, and GitHub PR data into a structured markdown report that highlights completed tasks and pending items.

Can I use workflow automation to track completed tasks and decisions from yesterday?▼

Yes, you can use workflow automation to track completed tasks and decisions by running this skill at the start of your workday to parse and aggregate your previous day's developer activity logs.

What logs are required to summarize pending items for a daily report?▼

Summarizing pending items for a daily report requires access to dev-os event logs to extract your previous day's tasks, session durations, and decisions, with GitHub CLI data added optionally.

Does the standup report skill work without dev-os event logs?▼

No, the standup report skill requires access to dev-os event logs to aggregate your completed tasks, sessions, and decisions, as this data forms the core of the generated activity summary.