daily-summary

Aggregate Graphite and GitHub CLI pull request statuses into Slack mrkdwn summaries.

4|Updated Oct 28, 2019
One-click install
npx skills add https://github.com/cfbender/dotfiles --skill daily-summary-cfbender
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-summary
Source: https://github.com/cfbender/dotfiles/tree/main/dot_agents/skills/daily-summary
Command: npx skills add https://github.com/cfbender/dotfiles --skill daily-summary-cfbender

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the tedious process of gathering and categorizing your work-in-progress, ready for review, and merged Pull Requests, streamlining your daily reporting.

Core Features & Use Cases

  • Automated PR Status Aggregation: Gathers data from Graphite and GitHub CLI.
  • Intelligent Categorization: Sorts PRs into Merged, Needs More Work, and Ready for Review.
  • Slack-Ready Formatting: Outputs a summary directly usable in Slack.
  • Use Case: At the end of your workday, run this Skill to instantly generate a clear summary of your contributions and outstanding tasks for your team's stand-up meeting.

Quick Start

Generate a daily work summary for the previous business day.

Frequently Asked Questions about daily-summary

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

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

To generate a daily standup summary, this Skill aggregates your pull request statuses from GitHub CLI and Graphite, categorizing them into merged, ready for review, and needing more work. It then formats the output for Slack.

Can I automate PR status aggregation for Slack reporting?

Yes, you can automate PR status aggregation for Slack reporting by running this Skill at the end of your workday. It retrieves PR data and outputs a Slack mrkdwn formatted summary with titles, links, and branch names.

Do I need Graphite and GitHub CLI to categorize pull requests?

Yes, you need both the Graphite (gt) and GitHub (gh) CLIs installed. The Skill depends on these command-line tools to retrieve pull request data and perform date manipulation for lookback periods.

How does PR categorization work for daily work summaries?

PR categorization for daily work summaries works by applying defined logic to sort pull requests fetched from GitHub and Graphite into three distinct states: Merged, Ready for Review, and Needs More Work.

What is the best way to summarize merged and in-progress pull requests?

The best way to summarize merged and in-progress pull requests is to use an automated script that queries your repositories via GitHub CLI and Graphite, categorizes the results, and formats them for standups.