fix-review

Analyze git commits against security audit findings to verify remediation.

1|Updated Jan 31, 2026

Search Tags:#security review #code audit #regression testing #vulnerability remediation #commit verification #fix validation

Ready to run

npx skills add https://github.com/allanninal/claude-code-skills --skill fix-review-allanninal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-review
Source: https://github.com/allanninal/claude-code-skills/tree/main/skills/fix-review
Command: npx skills add https://github.com/allanninal/claude-code-skills --skill fix-review-allanninal

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that code commits intended to fix security audit findings actually address the issues without introducing new bugs or vulnerabilities.

Core Features & Use Cases

Commit Verification: Analyzes code changes against specific security findings.
Regression Detection: Identifies if fixes introduce new security anti-patterns or bugs.
Use Case: After a security audit identifies a vulnerability (e.g., TOB-XYZ-123), developers push a fix. Use this Skill to confirm the commit(s) correctly remediate the issue and haven't broken anything else.

Quick Start

Verify that the commits in the 'fix-branch' correctly address the findings in the 'audit-report.pdf'.

Frequently Asked Questions about fix-review

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

FAQPage Schema

How do I verify that a git commit actually fixes a security audit finding?▼

To verify a git commit fixes a security audit finding, use differential analysis to compare code changes against documented vulnerabilities. This systematically checks fix branches to ensure specific finding IDs are remediated without introducing regressions.

What is differential analysis in vulnerability remediation?▼

Differential analysis in vulnerability remediation is the process of parsing git log and git diff outputs to compare code changes against security reports. It confirms that commits address documented vulnerabilities like TOB-XXX finding IDs without introducing new bugs.

How do I check a fix branch for new security anti-patterns after a code audit?▼

To check a fix branch for new security anti-patterns after a code audit, analyze the git diff against the original security report. This regression detection validates that vulnerability remediation commits do not inadvertently introduce new bugs.

Can I validate specific finding IDs like TOB-XXX against my git commits?▼

Yes, you can validate specific finding IDs like TOB-XXX against git commits. By parsing security reports and applying differential analysis to git diff outputs, the system systematically checks that your code changes address those exact documented vulnerabilities.

Do I need a specific security report format to validate fix commits?▼

You need a parsable security report format to validate fix commits effectively. The differential analysis process relies on parsing security reports to extract finding IDs and match them against the code changes identified in your git diff and git log outputs.

What are the limitations of using git diff for regression testing in security fixes?▼

A limitation of using git diff for regression testing in security fixes is that it requires accurate parsing capabilities for security reports. If the report format is unstructured or the commit history is fragmented, verifying vulnerability remediation becomes less reliable.