catchup

Generate a read-only project state snapshot with git status and pending tasks.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/SamyakJhaveri/loam --skill catchup-samyakjhaveri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: catchup
Source: https://github.com/SamyakJhaveri/loam/tree/main/seed/.claude/skills/catchup
Command: npx skills add https://github.com/SamyakJhaveri/loam --skill catchup-samyakjhaveri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fast 30s session bootstrap briefing. Use when resuming work after any break, at the start of a fresh session, or when unsure of current project state. Reports git status, recent commits, env state, memory staleness, pending tasks, and red flags (uncommitted changes, detached HEAD, stale memory). NOT for: deep codebase exploration, implementing changes, or running tests — only a read-only status snapshot.

Core Features & Use Cases

  • Provides a concise snapshot of the repository and environment at session start.
  • Reports git status, recent commits, and visible memory state to prevent wasted context switching.
  • Flags potential issues (uncommitted changes, detached HEAD, memory staleness) to guide safe continuation.
  • Use at session start, after breaks, or when unsure what to do next without modifying code.

Quick Start

Type /catchup to generate a concise project state snapshot.

Frequently Asked Questions about catchup

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

FAQPage Schema
How do I get a quick git status snapshot to resume work on a project?

To get a git status snapshot, use a read-only project briefing that reports recent commits, environment state, memory staleness, and pending tasks. This provides a fast 30-second overview to safely resume work without modifying code.

What is a session briefing for resuming software development work?

A session briefing is a read-only project state snapshot used at the start of a session or after breaks. It reports git status, recent commits, environment state, memory staleness, and pending tasks to prevent wasted context switching.

How do I check for red flags like uncommitted changes or detached HEAD before continuing work?

Checking for red flags involves running a read-only repository inspection that identifies uncommitted changes, detached HEAD states, and stale memory. This flags potential issues to guide safe continuation without making changes to the codebase.

When should I use a read-only project state snapshot in my workflow?

Use a read-only project state snapshot when resuming work after any break, at the start of a fresh session, or when unsure of the current repository state. It is not intended for deep codebase exploration, implementing changes, or running tests.

Does the catchup session briefing modify my repository or environment state?

The session briefing does not modify your repository or environment state. It is strictly a read-only inspection that reads git state, environment variables, memory index, and task lists to provide a concise status snapshot.