push-recap

To summarize daily git commits and pushes across multiple repositories, this skill fetches 24-hour push events and merged PRs via the gh api, ranking changes by impact to produce a concise verdict and deep recap.

Yes, you can separate user-visible code changes from internal churn. The recap analyzes daily push events and computes per-commit impact scores to distinguish meaningful shipments from routine internal churn.

You generate an automated daily recap of merged PRs by reading your configured watched repositories from memory, querying the gh api for recent merges, and formatting the results into a thematically grouped report.

Yes, you need the GitHub CLI to fetch commit data for push impact analysis. The skill directly interacts with the gh api to retrieve commits, pushes, and PR data from your watched repositories.

The best way to rank the impact of recent commits is computing a per-commit score based on 24-hour push events, which surfaces only meaningful changes and filters out low-value internal churn.

An automated push recap handles repository context by reading memory files including watched-repos.md and MEMORY.md, using this stored context to accurately filter and interpret recent push and PR activity.