rewind

Annotate file evolution from git history with change classifications.

71|7|Updated Apr 4, 2026

Search Tags:#git #analysis #diff #rewind #version-control #annotate #code-history

Ready to run

npx skills add https://github.com/mbwsims/claude-universe --skill rewind-mbwsims

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rewind
Source: https://github.com/mbwsims/claude-universe/tree/main/skills/rewind
Command: npx skills add https://github.com/mbwsims/claude-universe --skill rewind-mbwsims

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams understand how a file has evolved by presenting historical versions with annotated explanations of what changed and why.

Core Features & Use Cases

Annotated rewind: produces an explained evolution from historical to current versions.
Rename-aware history: detects file renames and traces continuity.
Change classification: groups edits into intentional design decisions, bug fixes, or accumulated patches.
Summarized reports: generates concise rewind reports and caches results for quick reuse.

Quick Start

Provide the target file path to rewind and run to generate an annotated history of changes.

Frequently Asked Questions about rewind

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

FAQPage Schema

How do I see the evolution of a file with annotated git history?▼

To see the evolution of a file with annotated git history, you provide the target file path to generate an explained rewind from historical to current versions, detailing what changed and why.

How does git change classification work for debugging sessions?▼

Git change classification for debugging works by grouping edits into intentional design decisions, bug fixes, or accumulated patches, helping you understand the reasoning behind modifications during code reviews.

Can I trace file renames in git history when reviewing code evolution?▼

Yes, you can trace file renames in git history when reviewing code evolution, as the rename-aware history feature detects file renames and traces continuity across the version control timeline.

Do I need access to the full git repository to generate code history reports?▼

Yes, you need access to the git repository history to generate code history reports, because the tool requires historical version data to produce annotated explanations and summarized rewind reports.

What is the best way to audit why changes happened in a codebase?▼

The best way to audit why changes happened in a codebase is to generate an annotated rewind report that classifies edits into design decisions or bug fixes and caches results for quick reuse.

Are there limitations when analyzing accumulated patches in version control?▼

A limitation when analyzing accumulated patches in version control is that the tool depends entirely on available git history data, meaning it cannot annotate changes if the repository history is missing or incomplete.