review-report

To generate a standardized code review report, collect findings from your code evaluation and trigger the skill to output a structured markdown file. It formats severity, domain, confidence, and evidence into a unified document for stakeholder handoff.

Yes, you can use this template-driven approach for multi-file commit code reviews. It supports any codebase undergoing evaluation, processing both single-file and multi-file commits to produce a unified review report with references.

A structured code review report includes severity levels, issue domains, confidence scores, evidence, and references. It summarizes quality, security, and performance issues by applying a standardized reference template to your collected findings.

Yes, the generated code review report integrates with reviewer-agent data formats. It ingests findings collected during code evaluation by reviewer agents and structures them into the standardized template for documentation and reproducibility.

The automated code review report output is saved as a markdown file. It is generated at docs/reports/code-review/ with a filename combining the commit hash and current date in YYYYMMDD format for traceability.