skills.rest
simota
simotaCOMMUNITY
Explore all skills by this author →
GitHub

Rewind

Analyzes Git history to identify commits that introduced regressions via git bisect.

68|14|Updated Jan 7, 2026
Search Tags:#git#debugging#root cause analysis#code history#regression#archaeology
One-click install
npx skills add https://github.com/simota/agent-skills --skill rewind
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Rewind
Source: https://github.com/simota/agent-skills/tree/main/rewind
Command: npx skills add https://github.com/simota/agent-skills --skill rewind

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers pinpoint the exact commit that introduced a bug or regression, and understand the historical context of code changes, enabling faster debugging and informed refactoring.

Core Features & Use Cases

  • Regression Root Cause Analysis: Automatically identifies the specific commit that broke functionality using git bisect.
  • Code Archaeology: Traces the evolution of code over time to understand design decisions and historical context.
  • Impact Analysis: Visualizes how code has changed and its potential ripple effects.
  • Use Case: A critical feature suddenly stopped working after a recent deployment. Rewind can be used to quickly identify which commit caused the failure, saving hours of manual debugging.

Quick Start

Use the Rewind skill to find the commit that introduced the bug reported in ticket #123.

Frequently Asked Questions about Rewind

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

FAQPage Schema
How do I find the commit that introduced a regression in my git history?▼

To find a regression in your git history, you can automate git bisect to identify the exact commit that broke functionality. This process systematically narrows down the code changes to pinpoint the root cause of the failure.

What is code archaeology and how does it trace code evolution?▼

Code archaeology traces code evolution by analyzing git blame and log history to understand design decisions. It visualizes change impact timelines to reveal the historical context and ripple effects of modifications.

How do I analyze the impact of code changes across different project types?▼

You can analyze the impact of code changes by visualizing change impact timelines across supported project types including game, SaaS, e-commerce, dashboard, and marketing applications to understand historical context and ripple effects.

Can I use git bisect to debug a critical feature that stopped working after deployment?▼

Yes, you can use automated git bisect to debug a feature that stopped working after deployment. It quickly identifies the specific commit that caused the failure, saving hours of manual debugging time.

Do I need any specific dependencies to perform root cause analysis on my repository?▼

No specific dependencies are required to perform root cause analysis on your repository. The skill operates independently using scripts and references to automate regression detection and trace code history.

Related Skills

Explore More Software Engineering Skills→
HouseGarofaloHouseGarofalo
3

git-workflow

Manage advanced Git workflows including rebase, cherry-pick, bisect, and reflog recovery.

Official
Advanced
viraatdasviraatdas

investigate

Identify bug root causes by collecting symptoms, reading code, and testing hypotheses.

Community
Advanced
jorgealvesjorgealves
2

technical-debt-visualizer

Aggregate complexity, test coverage gaps, and change frequency to identify high-risk code hotspots.

Community
Advanced
visualityplvisualitypl
4

debug

Analyze logs, SQLite database state, and git history to diagnose software issues.

Official
Intermediate