Annotate file evolution from git history with change classifications.
npx skills add https://github.com/mbwsims/claude-universe --skill rewind-mbwsims
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
This skill helps teams understand how a file has evolved by presenting historical versions with annotated explanations of what changed and why.
Provide the target file path to rewind and run to generate an annotated history of changes.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
ShmurdocAnalyze git commit history and code quality metrics to generate engineering retrospective reports.
lgzarturoCollect Git diffs and evaluate changes against a structured review checklist.
R2W1csLint and validate JavaScript and Python code for syntax and style issues.
chanhee-kangSplit and reorder Git commits into atomic changes with safe rebasing.
