home / skills / robzolkos / zolkos-agent-skills / catchup

catchup skill

safe

/skills/catchup

This skill helps you catch up on codebase changes by reviewing git diff against master and reading relevant specs.

npx playbooks add skill robzolkos/zolkos-agent-skills --skill catchup

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

402 B

---
name: catchup
description: Catch up on codebase changes by reviewing the diff from master and reading relevant spec files.
disable-model-invocation: true
allowed-tools: Bash(git *), Read, Glob
---

# Catch Up
> Execute the following sections to understand the codebase then summarize your understanding.

## Run
git diff master

## Read

Read any files that are in specs/ that are part of the diff

Overview

This skill helps an agent quickly catch up on recent codebase changes by inspecting the diff against master and reading any related spec files. It produces a concise understanding of what changed, why it matters, and which specs were updated. The goal is fast onboarding and focused review for follow-up work.

How this skill works

Run a git diff against the master branch to surface all file-level changes and hunks. Then open and read any files under specs/ that appear in the diff to extract updated requirements, test cases, or interface contracts. Finally, synthesize a short summary that links code changes to spec updates and highlights potential risks or action items.

When to use it

Before starting work on a feature branch to understand upstream changes.
When joining a pull request review to see the delta from master quickly.
During daily standups to summarize recent specification or behavior changes.
When verifying that code changes align with updated specs or tests.
After a merge to confirm nothing in specs/ was missed or misinterpreted.

Best practices

Run git diff master from the branch you want to evaluate to get an accurate delta.
Focus first on files in specs/ that appear in the diff; they often drive behavior and tests.
Note any mismatches between implementation and spec text as immediate action items.
Keep summaries short: list changed modules, updated specs, and one-sentence impact.
Record follow-up tasks such as test updates, documentation edits, or refactors.

Example use cases

A reviewer runs the diff to find which components were modified and reads updated specs to verify compliance.
A developer returning to a stalled task checks changes on master and reads spec updates to adjust implementation.
A team lead compiles a brief for stakeholders showing how recent commits altered product behavior and tests.
An automation script uses this process to generate a changelog entry that includes spec-driven changes.

FAQ

What exact command should I run?

Run git diff master from your current branch; for staged or committed only diffs add options like --name-only or commit ranges as needed.

Which spec files are relevant?

Any files under specs/ that appear in the diff are relevant—prioritize those that define behavior, interfaces, or acceptance tests.