catchup

To load project context before starting work, you can trigger a catchup workflow on your current branch to automatically read key files like CLAUDE.md, AGENTS.md, README.md, and configurations. It then surfaces actionable invariants, decisions, and health signals needed for informed work.

Reverse dependency tracing reveals the blast radius and rationale of changes by identifying linked issues and pull requests across your source files. This context helps you understand the potential impact of modifications before proceeding with a code review.

Yes, you need both gh and git installed as dependencies. The Skill uses git to read branch diffs and gh to trace linked issues and PRs, operating in parallel to assemble a structured capsule with project health signals.

The best way to surface invariants and decisions is to load raw sources directly rather than relying on summaries. The tool synthesizes a project capsule capturing derived insights, avoiding paraphrases of files to maintain context accuracy.

Large context windows are beneficial because the tool loads raw source files directly, including CLAUDE.md, AGENTS.md, and model directories, to hydrate context. It operates in parallel across sources to minimize wait times during loading.

Standard summaries often miss architectural decisions because they paraphrase files. The catchup tool avoids this by reading raw source files and configurations, directly capturing derived insights like invariants and blast-radius context into a structured capsule.