recap

Summarize git repository activity into a structured JSON recap file.

71|7|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/mbwsims/claude-universe --skill recap-mbwsims
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recap
Source: https://github.com/mbwsims/claude-universe/tree/main/skills/recap
Command: npx skills add https://github.com/mbwsims/claude-universe --skill recap-mbwsims

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill condenses recent repository activity into a concise, opinionated summary so a returning developer or reviewer can understand what landed, what was fixed, which areas received attention, and which parts may be neglected without wading through raw git logs.

Core Features & Use Cases

  • Period-aware history gathering: Parse user periods like "last sprint", "this month", or ISO dates and collect commits via timewarp MCP or git log.
  • Classification and grouping: Classify commits into features, fixes, refactors, tests, chores, and docs, group related commits by directory/time/message, and surface focused modules versus neglected areas.
  • Actionable output and caching: Present a human-friendly recap (features, fixes, focus, neglected, contributors) and save structured JSON to .timewarp/recap-YYYY-MM-DD.json for reuse in forecasting or drift analysis.

Quick Start

Run /recap or ask "recap the last 2 weeks" to generate a short summary of recent changes and save structured results to .timewarp/recap-YYYY-MM-DD.json.

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 repository activity for a specific time period?

Summarize recent git repository activity by parsing commit history for a specified period like last sprint or custom dates, classifying commits into features, fixes, and chores, then grouping changes by directory and contributor to output an actionable timeline.

What is the best way to find neglected codebase modules after a sprint?

To find neglected codebase modules, classify recent commit messages and files, group changes by directory and author, and surface focused modules versus neglected areas in a structured recap.

Can I generate a codebase activity report without timewarp MCP installed?

You can generate a codebase activity report without timewarp MCP by falling back to standard git log commands to parse commits, classify messages, and group changes by directory and author.

How do I classify git commits into categories like features, fixes, and refactors?

Classify git commits by parsing commit messages and changed files, grouping related commits by directory, time, and message, then categorizing them into distinct groups like features, fixes, refactors, tests, chores, and docs.

Does recap save structured commit history data for forecasting and drift analysis?

Recap saves structured commit history data by emitting structured JSON saved to .timewarp/recap-YYYY-MM-DD.json, enabling reuse in forecasting or drift analysis after presenting a human-friendly recap.

How do I group git changes by author and directory for a project timeline?

Group git changes by author and directory by parsing commits via timewarp MCP or git log, classifying messages and files, and emitting an actionable timeline of contributor actions and module focus areas.