audit-review-findings

Transform structured audit findings into traceable mixed-audience review reports with preserved evidence.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill audit-review-findings-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-review-findings
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/audit-review-findings
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill audit-review-findings-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw audit findings from code or Azure environment audits are machine-oriented and hard for mixed audiences to act on. This Skill converts them into traceable review reports that preserve every finding ID, severity, confidence level, evidence reference, and limitation without silently altering the source data. ## Core Features & Use Cases - Finding Classification: Reproduce or corroborate each finding and classify it as confirmed, needs-more-evidence, disputed, or false-positive with recorded rationale. - Schema-Preserving Output: Emit reviews matching source schema versions through 2.2, preserving auditRunId, assurance conclusions, and verification evidence exactly. - Actionable Guidance: Add resolution steps, alternatives, validation procedures, rollback guidance, and citations to Microsoft, OWASP, CWE, NIST, or CIS best practices. - Use Case: After running audit-code produces reports/code-audit-findings.json, invoke this Skill to generate code-audit-review.json and code-audit-review.md that security teams and developers can both consume before remediation planning. ## Quick Start Review the findings in reports/code-audit-findings.json and generate the validated code-audit-review.json and code-audit-review.md reports.

Frequently Asked Questions about audit-review-findings

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

FAQPage Schema
How do I review code audit findings before remediation planning?

Run this Skill on reports/code-audit-findings.json produced by audit-code. It validates the input schema, classifies each finding, adds resolution guidance and citations, and outputs code-audit-review.json and code-audit-review.md for downstream planning.

What inputs does the audit review process require?

It requires reports/code-audit-findings.json from audit-code or reports/azure-audit-findings.json from audit-azure-environment, plus the source revision and repository evidence cited by each finding. Input reports are validated against their declared schema before interpretation.

Can the review change severity or suppress findings?

No. Every source finding ID and evidence reference is preserved exactly, and findings cannot be silently added, merged, split, suppressed, or re-severed. Any severity change or false-positive decision must be explicit and justified in the output.

Does the review support schema 2.1 and 2.2 audit reports?

Yes. Reviews match the source schema version through 2.2. Schema 2.1 reviews preserve verificationEvidence exactly, and schema 2.2 reviews preserve auditRunId, immutable evidence references, assurance, and verification evidence.

When should I not use audit-review-findings?

Do not use it to discover new findings; it only reviews existing structured findings from audit-code or audit-azure-environment. It also does not schedule remediation, though it marks urgent containment separately from permanent repair.