fix-review

Name: fix-review
Availability: InStock
Author: monmacllcapp

Analyze git commit ranges against security audit reports to verify remediation and detect regressions.

Updated Aug 27, 2026

Search Tags:#code review #security #audit #bug detection #vulnerability remediation #commit verification

Ready to run

npx skills add https://github.com/monmacllcapp/skill-forks --skill fix-review-monmacllcapp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-review
Source: https://github.com/monmacllcapp/skill-forks/tree/main/skills/security/plugins/fix-review/skills/fix-review
Command: npx skills add https://github.com/monmacllcapp/skill-forks --skill fix-review-monmacllcapp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automatically verifies that code commits have correctly addressed security audit findings without introducing new bugs, ensuring that remediation efforts are effective and complete.

Core Features & Use Cases

Automated Verification: Compares code changes against security audit reports to confirm fixes.
Bug Detection: Scans commits for common security anti-patterns and potential regressions.
Use Case: After a security audit identifies several vulnerabilities (e.g., TOB-123, TOB-456), you can use this Skill to review the developer's fix branch, ensuring each finding is properly resolved and no new issues were created.

Quick Start

Use the fix-review skill to verify that commits from 'main' to 'fix-branch' address the security report located at '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 code commits actually fix security audit findings?▼

Security commit verification works by analyzing commit diffs between branches to detect security anti-patterns and potential regressions. It extracts findings from the provided audit report and maps code changes directly to remediation efforts for each identified vulnerability.

How do I review a fix branch to ensure vulnerability remediation is complete?▼

Review a fix branch by comparing commit ranges from the main branch against the security audit report. This differential analysis extracts identified findings and verifies that the code changes map successfully to the required vulnerability remediation efforts.

Can I use a PDF audit report to check git commits for security anti-patterns?▼

Yes, you can use a PDF audit report to check git commits. The analysis extracts findings from the provided report and scans the commit diffs for common security anti-patterns and potential regressions introduced during the remediation process.

Does commit verification detect potential regressions introduced during bug fixes?▼

Yes, commit verification detects potential regressions by scanning commit diffs for security anti-patterns. It ensures that developer code changes addressing audit findings do not inadvertently introduce new bugs or vulnerabilities into the codebase.

What is the best way to map code changes to vulnerability remediation efforts?▼

The best way to map code changes to vulnerability remediation efforts is through differential analysis. This method compares commit ranges against security audit reports, extracting findings and matching specific code modifications to verify complete remediation.