fxa-check-githistory

To catch regressions, this skill cross-references your current branch diff against historical commits on matching code paths. It identifies re-introduced bugs and conflicts with past fixes, summarizing risky changes with pointers to relevant prior commits for review.

Finding re-introduced bugs involves cross-referencing your current changes against prior commits on the same file paths. This skill surfaces patterns indicating conflicts with past fixes, providing a summary of risky changes with direct pointers to the relevant historical commits.

Analyzing git history to identify conflicts requires comparing your current branch diff against prior commits. This skill cross-references all changed files against repository history to surface patterns of regressions, re-introduced bugs, and conflicting changes across matching code paths.

Yes, you need access to a local git repository to check commits for regressions. This skill requires local repository access to cross-reference your current branch diff against historical commits on matching paths and summarize risky changes.

Yes, you can use this to review code changes for risky patterns before merging. By comparing your current branch diff against historical commits on matching code paths, it identifies regressions and re-introduced bugs, providing a summary of risky changes with pointers to relevant commits.