catchup

Audits memory, git state, PR queues, and project boards to produce a session briefing with one next action.

Updated Nov 1, 2024
One-click install
npx skills add https://github.com/mlorentedev/dotfiles --skill catchup-mlorentedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: catchup
Source: https://github.com/mlorentedev/dotfiles/tree/main/harness/skills/catchup
Command: npx skills add https://github.com/mlorentedev/dotfiles --skill catchup-mlorentedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Resuming work after a break, context compaction, or switching between parallel worktrees wastes time reconstructing what was done, what is in flight, and what to do next. This Skill automates that reconstruction by auditing memory files, live git state, PR triage queues, and project boards, then delivering a single executive briefing. ## Core Features & Use Cases - Memory Continuity Ingestion: Reads the session handoff block in MEMORY.md and resolves the correct thread for the current session before anything else. - Live Git & Worktree Audit: Verifies branch, dirty files, worktrees, gone branches, and open PRs via git and gh commands. - PR Triage & Board Check: Runs the PR triage queue and lists In Progress/Blocked items on the GitHub project board. - Executive Briefing Output: Produces a structured health-status report ending with exactly one unambiguous next action and the command to run it. - Use Case: At the start of a coding session, invoke the catchup trigger to instantly learn that your branch is dirty, a PR review is pending triage, and the next action is to triage PR #42 before writing new code. ## Quick Start Ask the assistant to run the catchup briefing, for example by saying "catch me up on this repo and tell me what to do next".

Frequently Asked Questions about catchup

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

FAQPage Schema
How do I resume a coding session after losing context?

Run the catchup briefing, which reads the session handoff block in MEMORY.md, audits live git state, checks the PR triage queue, and lists active board items. It concludes with exactly one next action and the command to execute it.

How to check open PRs and triage status before starting new work?

The briefing runs gh pr list for open PRs and dotf pr triage-queue to detect un-triaged reviewer output. An exit code of 1 means triaging that PR takes precedence over any new feature work.

Does the catchup briefing work with multiple git worktrees?

Yes, it audits git worktree list to detect orphan or merged trees and resolves which session thread belongs to the current worktree before reading handoff notes. This prevents inheriting a next action meant for a parallel session.

What tools are required to run this session briefing?

It requires git, the GitHub CLI (gh) for PR and project board queries, python3 for JSON parsing, and the dotf CLI for memory thread lookup and PR triage. It also reads vault files like MEMORY.md and context.md.

Why does the briefing output only one next action?

The Rule of One forces prioritization so the session starts with a single unambiguous step instead of a diffuse task list. Additional findings like technical debt are ticketed separately rather than competing for immediate attention.