catchup

Summarize merged and open PR activity into a net-effects briefing.

20|4|Updated Jan 7, 2026

Search Tags:#git #codebase #analysis #synthesis #triage #pull-request #briefing

Ready to run

npx skills add https://github.com/nbramia/LifeOS --skill catchup-nbramia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: catchup
Source: https://github.com/nbramia/LifeOS/tree/main/.agents/skills/catchup
Command: npx skills add https://github.com/nbramia/LifeOS --skill catchup-nbramia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synthesizes recent PR activity into a focused net-effects briefing, helping teams understand changes quickly without reading every PR.

Core Features & Use Cases

Net-effects briefing: condense merged and open PR activity into a structured narrative.
Time-window scope: adjust the reporting window (e.g., last 24 hours, 7 days) and apply author filters (me/others).
Triage and summary: categorize changes by theme and provide a high-level impact assessment for stakeholders.

Quick Start

Provide a time window and optional author filter to generate a concise net-effects briefing for the current codebase.

Frequently Asked Questions about catchup

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

FAQPage Schema

How do I summarize recent pull request activity for a specific time window?▼

Summarize recent pull request activity by condensing merged and open PRs within a defined time window into a concise net-effects briefing. This categorizes codebase changes by theme to help stakeholders understand impact quickly.

What is a net-effects briefing for git pull requests?▼

A net-effects briefing for git pull requests is a structured narrative summarizing landed and in-flight codebase changes. It aggregates additions and deletions to provide a high-level impact assessment without reading every PR.

Can I filter pull request summaries by author or specific time periods?▼

Yes, you can filter pull request summaries by applying author filters such as me, others, or all. You can also adjust the reporting time window scope to target specific periods like the last 24 hours or 7 days.

Does generating a PR briefing require access to the local repository and gh?▼

Yes, generating a PR briefing requires access to gh and the local repository state. This access is needed to compute landed versus in-flight PRs and aggregate codebase additions and deletions accurately.

What is the best way to triage open and merged pull requests in a codebase?▼

The best way to triage open and merged pull requests is to synthesize the activity into a focused net-effects briefing. This categorizes changes by theme and provides a high-level impact assessment for stakeholders.

When should I use an automated PR briefing instead of reading individual pull requests?▼

You should use an automated PR briefing when teams need to understand codebase changes quickly without reading every PR. It helps triage and synthesize merged and open PR activity into a concise summary for a defined time window.