Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/catchup
Summarizes recent git changes for context recovery after session breaks.
Passed 18 of 22 test cases with the skill, and 11 of 22 without it.
and 6 more in the full report
7 fixed11 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before running repository inspection commands during a git catchup workflow, what flag should be executed with the command to verify tool availability in the environment?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies executing the --help flag to verify availability. | Missed | Passed |
The instructions your model reads when the skill loads.
Structured method for quickly understanding recent changes in git repositories, meeting notes, sprint progress, document revisions, or system logs. Answers "what changed and what matters?" efficiently.
Keywords: catchup, summary, status, progress, context, handoff Cues: "get me up to speed", "current status", "summarize progress"
Load modules based on context:
Git: Load modules/git-catchup-patterns.md for git commands. Consider sanctum:git-workspace-review for initial data gathering.
Documents/Notes: Load modules/document-analysis-patterns.md for meeting notes, sprint tracking, document revisions.
Logs/Events: Load modules/log-analysis-patterns.md for time-series and metric analysis.
Always Available: imbue:proof-of-work, TodoWrite workflow, structured output.
catchup:context-confirmed - Boundaries establishedcatchup:delta-captured - Changes enumeratedcatchup:insights-extracted - Themes identifiedcatchup:followups-recorded - Actions capturedtest cases passed, vs 11 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.