recap

Summarize recent git commits and outline next steps from a local recap journal.

1|Updated May 30, 2026
One-click install
npx skills add https://github.com/FixPortal/fixportal-claude-skills --skill recap-fixportal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recap
Source: https://github.com/FixPortal/fixportal-claude-skills/tree/main/skills/recap
Command: npx skills add https://github.com/FixPortal/fixportal-claude-skills --skill recap-fixportal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Recap helps you quickly summarize progress and plan next actions after a pause by analyzing recent commits, repository state, and a local journal.

Core Features & Use Cases

  • Generates a concise, delta-driven summary of changes since the last recap.
  • Classifies items into Actionable Now, Deferred, Unverifiable, Operator Gated, and Information Only.
  • Maintains a local recap journal under ~/.claude/recap and updates it when there are new commits.

Quick Start

Run the recap to generate a delta-driven digest of new commits since the last recap and surface next steps.

Frequently Asked Questions about recap

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

FAQPage Schema
How do I summarize recent git commits after a project pause?

Recap classifies journal entries and git deltas into Actionable Now, Deferred, Unverifiable, Operator Gated, and Information Only buckets, helping you map and prioritize next steps after a context switch.

What is a git journaling workflow for planning next steps?

Recap requires a local git repository with existing history and a local recap journal stored under ~/.claude/recap to compute deltas and classify items into action buckets.

Do I need a local journal to generate a git commit summary?

Recap operates on local git repositories with a journaling workflow, analyzing commits, branches, and workspace state to produce a structured recap without needing external dependencies.

What's the best way to plan next actions after a context switch in git?

You can run the recap to generate a delta-driven digest of new commits since the last recap and surface next steps, providing a structured summary of progress and planned actions.