fix-review

Identify changed identifiers and verify call sites after code fixes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/emanuelrechsteiner/FairSplit --skill fix-review-emanuelrechsteiner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-review
Source: https://github.com/emanuelrechsteiner/FairSplit/tree/main/.claude/skills/fix-review
Command: npx skills add https://github.com/emanuelrechsteiner/FairSplit --skill fix-review-emanuelrechsteiner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

After making a code fix, developers need to confirm the fix is complete across the codebase and that no related issues were introduced. This skill provides a structured post-fix verification workflow that identifies changed scopes, locates all related occurrences, and checks that call sites and cascading changes are updated correctly.

Core Features & Use Cases

  • Identify changed identifiers and affected files from a patch or diff.
  • Search the repository for related usages, type/interface changes, and import paths.
  • Verify all affected call sites and interfaces to prevent regressions or misaligned updates.
  • Detect cascading issues to ensure the fix does not introduce downstream problems.
  • Use Case: after fixing a bug, run the review to ensure nothing was missed and the fix is fully propagated.

Quick Start

Run the fix-review process after applying a bug fix to verify the scope, locate all related occurrences, and confirm call sites and cascading changes are correct.

Frequently Asked Questions about fix-review

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

FAQPage Schema
How do I verify a bug fix is complete across my codebase?

Verifying a bug fix requires identifying changed identifiers and searching the codebase for all related occurrences. This skill cross-checks diffs and reference usage to confirm call sites and cascading changes are updated correctly, preventing missed updates.

What is the best way to check for regressions after modifying an interface?

Checking for regressions after modifying an interface involves searching for all related usages and import paths. This skill performs a diff analysis to verify affected call sites and interfaces, ensuring changes align with the original intent and preventing downstream problems.

How do I find all affected call sites after a code change?

Finding affected call sites requires analyzing the patch to identify changed identifiers and affected files. This skill searches the repository for related usages and type changes, verifying call-site integrity to ensure the fix is fully propagated.

Can I use this to detect cascading issues from a recent patch?

Yes, you can detect cascading issues by analyzing the scope of a recent code fix. This skill cross-checks diffs and reference usage to identify potential downstream problems, ensuring the patch does not introduce misaligned updates or new regressions.

Does this post-fix review workflow require any specific dependencies?

No specific dependencies are required to run this post-fix review workflow. It applies to typical software projects by analyzing diffs and repository references directly to verify changes and ensure call-site integrity.