daily-report

Generate daily GitHub organization activity reports covering commits, PRs, branches, issues, force-pushes, and CI failures.

3|1|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/nsheaps/ai-mktpl --skill daily-report-nsheaps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-report
Source: https://github.com/nsheaps/ai-mktpl/tree/main/plugins/daily-report/skills/daily-report
Command: npx skills add https://github.com/nsheaps/ai-mktpl --skill daily-report-nsheaps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating a complete, consistent daily summary of activity across a GitHub organization is time-consuming and error-prone when done manually. This Skill centralizes data gathering and formatting so teams receive a single, actionable Markdown report covering commits, PRs, branches, issues, force-pushes, and CI failures.

Core Features & Use Cases

  • Organization-wide aggregation: Scans all repositories (or a specified subset) and aggregates commits, pull requests, branch events, issue changes, and workflow failures within a chosen time window.
  • Force-push and audit analysis: Detects force pushes via audit log or events API, preserves before/after SHAs, and surfaces potential lost commits and regressions.
  • Actionable attention callouts: Produces an immediate "Attention Required" section highlighting agent failures, repeated CI failures, and items needing human intervention suitable for posting as a GitHub issue.
  • Use Case: Ideal for SREs and engineering managers who need a daily digest of repo health, CI flakiness, and potential automated-agent churn across an organization.

Quick Start

Generate a daily report for organization nsheaps covering the last 1 day and post it as a GitHub issue.

Frequently Asked Questions about daily-report

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

FAQPage Schema
How do I generate a daily GitHub organization activity report?

Generate a daily GitHub organization activity report by scanning all repositories to aggregate commits, pull requests, branch events, issue changes, and CI failures into a single Markdown summary. The Skill requires GitHub API access via the gh CLI with an org-scoped token.

Can I detect force-pushes across a GitHub organization?

Detect force-pushes across a GitHub organization using audit log or events API fallbacks. The report preserves before and after SHAs to surface potential lost commits and regressions for review.

What is the best way to aggregate CI failures and pull requests across multiple GitHub repositories?

Aggregate CI failures and pull requests across multiple repositories by defining a time window for the organization scan. The Skill compiles workflow failures, PR activity, and issue changes into an actionable Markdown report.

Do I need an org-scoped token to aggregate GitHub commits for a daily report?

An org-scoped token is required to aggregate GitHub commits for a daily report. You must authenticate using the gh CLI to ensure the Skill has sufficient permissions to access organization audit logs and repository events.

How does the daily report handle repeated CI failures and agent churn?

The daily report handles repeated CI failures by producing an Attention Required section highlighting agent failures and items needing human intervention. This section is formatted for direct posting as a GitHub issue.

Can I limit the daily organization report to a specific subset of repositories?

You can limit the daily organization report to a specific subset of repositories. The Skill allows you to specify which repositories to scan within the chosen time window for commits, PRs, and CI failures.