review-output

Format code review findings into a standardized Markdown structure.

19|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/xobotyi/cc-foundry --skill review-output
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-output
Source: https://github.com/xobotyi/cc-foundry/tree/main/plugins/the-crucible/skills/review-output
Command: npx skills add https://github.com/xobotyi/cc-foundry --skill review-output

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a consistent, machine-readable format for reporting code review findings, making it easier to parse, aggregate, and act upon feedback from various review agents.

Core Features & Use Cases

  • Standardized Reporting: Enforces a uniform structure (Critical, Issues, Recommendations, Good Patterns, Summary) for all code review outputs.
  • Automated Parsing: Enables downstream tools and agents to reliably process review results.
  • Use Case: After a security review agent runs, its findings are automatically formatted into a SKILL.md-compliant report file, ready for integration into a CI/CD pipeline or a project management tool.

Quick Start

Use the review-output skill to format the findings from the security review of the 'auth-module.py' file.

Frequently Asked Questions about review-output

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

FAQPage Schema
How do I standardize code review findings for automated parsing?

You can standardize code review findings by applying a Markdown format that categorizes results into Critical, Issues, Recommendations, and Good Patterns, enabling reliable automated parsing and aggregation of review outputs.

What is a standardized code review reporting format?

A standardized code review reporting format is a uniform Markdown structure that categorizes findings by severity, allowing downstream tools and CI/CD pipelines to reliably process security, quality, and documentation checks.

How do I integrate code review reports into a CI/CD pipeline?

You integrate code review reports into a CI/CD pipeline by formatting agent findings into a machine-readable Markdown report file, which downstream tools can automatically parse and act upon.

Does automated code review reporting require specific severity mappings?

Yes, automated code review reporting requires adherence to specific output structures and severity mappings to ensure consistent agent communication and reliable aggregation of review results.

Can I aggregate security and quality review results from different agents?

Yes, you can aggregate security and quality review results from different agents by enforcing a uniform reporting structure, which makes it easier to parse and act upon feedback from various review agents.

What categories should I use when formatting code review findings?

When formatting code review findings, you should use four specific categories: Critical, Issues, Recommendations, and Good Patterns, along with a Summary section for complete reporting.