catchup

Compare the working branch with master and read modified specs.

3|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/robzolkos/zolkos-agent-skills --skill catchup-robzolkos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: catchup
Source: https://github.com/robzolkos/zolkos-agent-skills/tree/main/skills/catchup
Command: npx skills add https://github.com/robzolkos/zolkos-agent-skills --skill catchup-robzolkos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Catch up on codebase changes by reviewing the diff from master and reading relevant spec files that were modified.

Core Features & Use Cases

  • Compare working changes against master to surface only relevant diffs.
  • Identify touched specs and files to inform debugging and integration work.
  • Use during handoffs to quickly align on updated expectations.

Quick Start

Run git diff master to see the latest changes and read any specs listed in the diff.

Frequently Asked Questions about catchup

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

FAQPage Schema
How do I catch up on code changes from a master branch diff?

To catch up on code changes from a master branch diff, you compare your working branch against master to surface relevant diffs and read any modified spec files to understand updated expectations.

What is the best way to review modified specs during a task handoff?

Reviewing modified specs during a task handoff is best done by performing a git diff against master and reading any specs listed in the diff to quickly align on updated project expectations.

How does comparing the working branch with master help with code review?

Comparing the working branch with master helps with code review by identifying touched specs and files, which surfaces only the relevant diffs needed to inform debugging and integration work.

Does this git diff workflow require any special dependencies to read touched files?

No special dependencies are required for this git diff workflow to read touched files. It executes deterministic steps using standard git commands to compare branches and read modified specs.

Can I use this to find only the specs that changed in my working branch?

Yes, you can use this to find only the specs that changed in your working branch. It identifies touched specs by checking the diff against master and reading any specs under the specs/ directory that are part of the diff.