fix-review

Trace git commits to security audit findings and generate remediation reports.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/baskarajati/undangan --skill fix-review-baskarajati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-review
Source: https://github.com/baskarajati/undangan/tree/main/.agent/skills/fix-review
Command: npx skills add https://github.com/baskarajati/undangan --skill fix-review-baskarajati

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Verifies that git commits address security audit findings without introducing bugs. This skill should be used when the user asks to "verify these commits fix the audit findings", "check if TOB-XXX was addressed", "review the fix branch", "validate remediation commits", "did these changes address the security report", "post-audit remediation review", "compare fix commits to audit report", or when reviewing commits against security audit reports.

Core Features & Use Cases

  • Cross-checks findings against commit changes to ensure root causes are addressed
  • Maps TOB identifiers and remediation notes to specific commits and diffs
  • Generates a structured audit-ready report with evidence and recommendations
  • Use case: validating a multi-commit remediation across several files after a security alert

Quick Start

Provide the source and target commit hashes, and optionally an audit report path, to run an automated fix-review pass

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 git commits actually fix security audit findings?

To verify commits fix security audit findings, you can use an automated fix-review process that traces specific commits to identified vulnerabilities and assesses whether the changes address the root causes. This produces an evidence-backed report confirming remediation coverage.

How do I check if TOB identifiers in a security report were addressed in remediation commits?

You can check if TOB identifiers were addressed by mapping the remediation notes and TOB tags to specific commits and diffs. This commit analysis cross-references the audit report against the code changes to validate root cause remediation.

What's the best way to review a fix branch against a security audit report?

The best way to review a fix branch against a security report is to perform an automated post-audit remediation review. This compares the fix commits to the audit findings and generates an auditable, structured report with evidence and risk notes.

Does commit analysis for security fixes evaluate root causes or just surface-level patches?

Commit analysis for security fixes evaluates root causes rather than just surface-level patches. It cross-checks the audit findings against the code changes to ensure the underlying security vulnerabilities are fully addressed without introducing bugs.

Can I validate a multi-commit remediation across several files after a security alert?

Yes, you can validate a multi-commit remediation across several files after a security alert. The fix-review process traces multiple commits to the identified findings and produces an audit-ready report with remediation coverage and risk notes.

What do I need to provide to run an automated fix-review pass on my code?

To run an automated fix-review pass, you need to provide the source and target commit hashes. You can also optionally provide an audit report path to cross-check the commit changes against the identified security findings.