catch-up
Find out what changed before you start changing it again.
Coming back to a busy branch shouldn’t mean reading twenty commit messages and guessing what matters. Catch Up reads the actual changes, groups them by feature, and points out what affects the work in front of you.
When I’d use it
Use it after a break, before working in an unfamiliar area, or when you want to understand what a pull would bring in. It is read-only unless you explicitly ask it to save a checkpoint.
Before you start
Open a Git repository. By default it starts from your most recent authored commit reachable from the target. If that isn’t the right baseline, give it a ref, date, or number of changes.
Install it. Then give it a task.
Run this in your project’s terminal. Choose your coding agent in the installer, then start a new agent session if it needs one to discover the skill.
$ npx skills add akdevsaha-dev/factory-skills --skill catch-upOnce installed, send a prompt like the ones below to your agent. These are example requests to adapt to your own project, not terminal commands or recorded results.
If slash commands aren’t available in your agent, write “Use the catch-up skill to…” and describe the same task.
New to skills? Start with the installation walkthroughWhat happens next
- Resolves and shows the target and baseline.
- Reads the net diff, with more depth for contracts, migrations, config, and other high-signal changes.
- Groups related work and connects it to your local changes.
- Reports concrete locations, risks, and what deserves a closer look.
A few ways to ask
6 examplesCopy the one closest to your task. Replace names, paths, dates, and refs with ones that exist in your project.
The everyday briefing
› /catch-upStarts with a quick briefing against local HEAD.
Use a clear baseline
› /catch-up since mainReplace main with the branch or commit that represents where you left off.
Look back a few changes
› /catch-up last 5Counts units of change along the target’s first-parent history.
Inspect the remote view
› /catch-up deep remoteUses the remote-tracking refs already on your machine. It does not fetch, so check when those refs were last updated.
Narrow it to a teammate
› /catch-up since 2026-11-01 author alexReplace the date and author with your own. Findings outside that author’s work may still matter to your local changes.
Create a return point
› /catch-up saveExplicitly asks to save the analyzed commit as a checkpoint. Next time, use /catch-up checkpoint.
What to look for in the result
A feature-based briefing with a resolved range and file locations. It shouldn’t pull, merge, fetch, switch branches, or edit the working tree. Remote analysis is only as fresh as your local tracking refs.
A thing worth watching
An empty range can be correct. Change the baseline if you want a different window. “Remote” means inspect available refs, not contact the server for new commits.
Use it with
Build a workflow you can repeat.
Follow the step-by-step guide to working with agents.