catchup-recent

Review staged and unstaged Git changes with git status --short.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/EtanHey/golems --skill catchup-recent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: catchup-recent
Source: https://github.com/EtanHey/golems/tree/main/skills/golem-powers/catchup-recent
Command: npx skills add https://github.com/EtanHey/golems --skill catchup-recent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you quickly get back up to speed on your current work after a short break by showing you only the uncommitted changes in your repository.

Core Features & Use Cases

  • Context Recovery: Ideal for short breaks (hours, not days) to refresh your memory on what you were working on.
  • Uncommitted Changes Focus: Specifically reads staged and unstaged modifications, ignoring committed history.
  • Use Case: You stepped away for lunch and want to quickly see what files you were editing before you continue coding.

Quick Start

Use the catchup-recent skill to review your current uncommitted changes.

Frequently Asked Questions about catchup-recent

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

FAQPage Schema
How do I quickly check uncommitted changes in git after a break?

To check uncommitted changes in git, you need a tool that scopes to staged and unstaged modifications. This skill reads modified files using `git status --short` to provide rapid context recovery for your current work.

What is the best way to refresh my memory on staged and unstaged git modifications?

Refreshing your memory on staged and unstaged git modifications is best done by viewing a rapid overview of uncommitted changes. This approach specifically targets modified files, ignoring committed history, to help you resume coding.

Does this context recovery method show committed git history?

No, this context recovery method does not show committed git history. It specifically focuses on reading staged and unstaged modifications within your git repository to provide immediate context after brief interruptions.

How do I see what files I was editing before I continue coding?

To see what files you were editing before you continue coding, you can review your current uncommitted changes. This provides a quick summary of modified files, ideal for context recovery after stepping away for lunch.

Can I use `git status --short` to identify modified files for context recovery?

Yes, you can use `git status --short` to identify modified files for context recovery. This skill requires executing that exact command to scope uncommitted code modifications and rapidly refresh your current work state.