fix-review

Name: fix-review
Availability: InStock
Author: fjor1025

Analyze git commits against security audit findings to verify fixes.

Updated Feb 13, 2026

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

Ready to run

npx skills add https://github.com/fjor1025/InfoSec-Framework --skill fix-review-fjor1025

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-review
Source: https://github.com/fjor1025/InfoSec-Framework/tree/main/ClaudeSkills/plugins/fix-review/skills/fix-review
Command: npx skills add https://github.com/fjor1025/InfoSec-Framework --skill fix-review-fjor1025

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that code changes intended to fix security vulnerabilities actually resolve the issues without introducing new bugs or regressions.

Core Features & Use Cases

Commit Verification: Analyzes git commits against security audit reports to confirm findings are addressed.
Bug Introduction Detection: Scans changes for common anti-patterns that indicate new vulnerabilities.
Use Case: After a security audit identifies several critical issues, developers push fixes to a new branch. Use this Skill to automatically review those commits, confirm each finding is resolved, and ensure no new problems were created.

Quick Start

Use the fix-review skill to verify that commits from 'main' to 'fix-branch' have addressed the findings in '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 git commits address security audit findings without introducing bugs?▼

To verify git commits address security audit findings without introducing bugs, perform a differential analysis against audit reports. This process checks fix branches to confirm vulnerabilities are resolved while scanning changes for common anti-patterns indicating new regressions.

Can I validate specific security findings like TOB-XXX against my fix branch?▼

Yes, you can validate specific security findings like TOB-XXX against your fix branch. The differential analysis checks targeted findings by comparing git commits from the main branch against the remediation branch using the provided security report.

What report formats can I use for security audit remediation review?▼

For security audit remediation review, supported report formats include PDF, Markdown, JSON, and HTML. The analysis reads these files to cross-reference identified vulnerabilities with the code changes implemented in your git commits.

Does git commit verification work for post-audit remediation across different branches?▼

Git commit verification works for post-audit remediation by analyzing changes between branches. It compares commits from the base branch to the fix branch, confirming security findings are addressed and ensuring no new vulnerabilities are created in the process.

How does bug introduction detection work when reviewing vulnerability remediation?▼

Bug introduction detection works by scanning code changes for common anti-patterns during vulnerability remediation. It performs differential analysis on git commits to identify new vulnerabilities or regressions introduced while attempting to resolve original security findings.

What is needed to start checking fix branches against security reports?▼

To start checking fix branches against security reports, you need git installed and optionally tools for reading various report formats like PDF, MD, JSON, or HTML. Web fetching tools may also be utilized to access external documentation during the differential analysis.