Analyze Git history to identify code changes and regressions.
npx skills add https://github.com/nielsmadan/agentic-coding --skill review-history
Please help me install this Agent Skill. Skill: review-history Source: https://github.com/nielsmadan/agentic-coding/tree/main/claude/skills/review-history Command: npx skills add https://github.com/nielsmadan/agentic-coding --skill review-history
This Skill helps you understand how code has changed over time, which is crucial for debugging regressions, understanding design decisions, and identifying when specific behaviors were introduced.
Use the review-history skill to analyze the git history of the file src/auth/login.ts.
High-intent search queries and answers about installing and using this skill.
To trace when a behavior was introduced in git history, you analyze recent commits and blame information for the relevant files. This pinpoints the exact code introduction and helps uncover the original design rationale behind the change.
Finding a regression by comparing code states across commits involves inspecting the git history of affected files. By reviewing detailed blame information and recent commits, you can pinpoint the exact change that caused the feature to stop working.
Yes, you can use git blame to investigate past issues and bug reports. The process correlates detailed blame information with past issue logs, providing context on how specific code changes relate to previous bug reports or feature requests.
Analyzing git history to understand design rationale requires inspecting the commit history and blame information of the specific code. This reveals how the code evolved over time and shows the exact introductions that shaped the current architecture.
Yes, you need access to a git repository to review code evolution and recent commits. The skill requires a repository to inspect detailed blame information and track specific code introductions for debugging regressions.
Reviewing past commit history helps with debugging regressions because it identifies exactly when a bug was introduced. By comparing code states across recent commits, you can isolate the specific change that caused the unwanted behavior.
rloisellDefine and enforce Git workflow conventions for branch naming, commit messages, and PR titles.
guccangCreate failing tests before implementing minimal production code.
zangjeicyScan git diffs for security vulnerabilities and quality regressions.
robit-manAutomate git bisect to identify the commit that introduced a regression.
