push-recap

Summarize daily GitHub push activity with impact-ranked commit categories.

6|2|Updated May 21, 2026

Search Tags:#github actions #commit analysis #release communication #push recap #impact ranking #diff summarization #autonomous reporting

Ready to run

npx skills add https://github.com/anajuliabit/aeon --skill push-recap-anajuliabit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: push-recap
Source: https://github.com/anajuliabit/aeon/tree/main/skills/push-recap
Command: npx skills add https://github.com/anajuliabit/aeon --skill push-recap-anajuliabit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Push recaps eliminate the effort of manually reading diffs by summarizing what actually shipped, what changed internally, and what likely matters to users each day.

Core Features & Use Cases

Signal-gated daily digest: Filters bot/dependency noise and suppresses notifications on low-signal days instead of spamming.
Impact ranking with user-visible vs internal split: Ranks commits by impact and categorizes them into shipped to users, under the hood, and infra.
Theme-based deep recap and verdict: Produces a one-line verdict plus clustered themes with actionable summaries, using recent history from the last 2 days.

Quick Start

Give the agent the command: set var to an owner/repo value like "acme/my-service" to generate your daily recap for just that repository.

Frequently Asked Questions about push-recap

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

FAQPage Schema

How do I summarize daily GitHub push activity across watched repositories?▼

You can summarize daily GitHub push activity by fetching the last 24 hours of push events and commits, pulling merged PRs as thematic anchors, and generating an article ranking commit impact across configured repositories.

How does impact ranking distinguish user-visible shipping from internal churn?▼

Impact ranking distinguishes user-visible shipping from internal churn by categorizing commits into shipped changes, under-the-hood updates, and infrastructure, while applying bot and significance gating to suppress low-signal noise.

Can I generate a daily commit recap for a single specific repository?▼

Yes, you can generate a daily commit recap for a single specific repository by setting a variable to an owner/repo value like "acme/my-service", which scopes the push event fetching and diff summarization to that repo.

What happens to the recap notification on days with only bot or dependency commits?▼

On days with only bot or dependency commits, the recap notification is suppressed entirely by signal-gating logic that enforces significance thresholds to prevent low-signal spam instead of sending empty alerts.

How are partial fetch failures handled when reading push events and commits?▼

Partial fetch failures are handled safely during push event and commit retrieval, ensuring the recap output includes source-status attribution to indicate which watched repositories successfully returned data versus which encountered fetch errors.