push-recap

Generates daily ranked recaps of GitHub pushes separating user-visible shipments from internal work.

Updated May 25, 2026
One-click install
npx skills add https://github.com/Cbowcrptex/CBOWCRYPTEX --skill push-recap-cbowcrptex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: push-recap
Source: https://github.com/Cbowcrptex/CBOWCRYPTEX/tree/main/skills/push-recap
Command: npx skills add https://github.com/Cbowcrptex/CBOWCRYPTEX --skill push-recap-cbowcrptex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw chronological commit lists bury the answer readers actually want: what shipped to users today, what is internal churn, and what is stuck. This Skill turns noisy GitHub push activity into a ranked, verdict-led daily recap. ## Core Features & Use Cases - Impact-ranked commit analysis: Reads diffs via the GitHub CLI, classifies commits as user-visible, internal, or infra, and scores them by impact. - Verdict-led reporting: Writes a one-line verdict (SHIPPING, BUILDING, HARDENING, REFACTORING, MAINTAINING, or MIXED) plus a themed deep-dive article saved to articles/. - Signal-gated notifications: Suppresses notifications on quiet days and filters bot commits so channels stay high-signal. - Use Case: A maintainer watching several repos runs the recap each morning to get a notification naming exactly what shipped, with a linked article detailing diffs, merged PRs, and open threads. ## Quick Start Run the push-recap skill to summarize all pushes across my watched GitHub repos from the last 24 hours.

Frequently Asked Questions about push-recap

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

FAQPage Schema
How do I get a daily summary of GitHub commits and pushes?▼

Run the push-recap skill, which fetches push events and commits from the last 24 hours via gh api, ranks them by impact, and writes a themed recap article plus a concise notification. It reads watched repos from memory/watched-repos.md or bootstraps from your git remote.

How to filter bot commits like dependabot from GitHub activity reports?▼

The skill drops commits from dependabot[bot], renovate[bot], github-actions[bot], and *-bot authors, plus chore(deps): messages, unless they touch files outside lockfiles and .github/. The filtered count is reported in the article footer.

Can I recap pushes for only one specific GitHub repository?▼

Yes. Pass the repo in owner/repo format as the var parameter and the skill recaps only that repository. If left empty, it recaps every repo listed in memory/watched-repos.md.

What happens when there were no significant commits in a day?▼

If bot-filtering leaves zero commits across all watched repos, the skill logs PUSH_RECAP_QUIET and stops without sending a notification or writing an article. Low-signal days with no user-visible commits and few internal ones are also suppressed.

Does the GitHub recap handle API rate limits or fetch errors?▼

Yes. Rate-limited or failed fetches are recorded per repo and the skill continues with partial data. Every article ends with a source-status footer showing ok, rate-limited, partial, empty, or error per repo and per gh command.