code-review

Review code diffs for beads or features and generate formal severity-based reports.

157|12|Updated Feb 2, 2026

Search Tags:#quality-assurance #code-review #diff-analysis #engineering-process #auditable-reports #bead-review

Ready to run

npx skills add https://github.com/dcosson/h2 --skill code-review-dcosson

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/dcosson/h2/tree/main/internal/config/templates/styles/opinionated/skills/code-review
Command: npx skills add https://github.com/dcosson/h2 --skill code-review-dcosson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to perform structured, independent reviews of code diffs after bead or feature implementation, producing formal review artifacts that support quality assurance and auditability.

Core Features & Use Cases

Structured review workflow that generates a formal document with findings and severity levels.
Independent validation focused on actual code changes rather than plans or assumptions.
Output suitable for integration into CI/CD processes and project documentation.

Quick Start

Run a code-review for bead-XYZ to generate the initial review document.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I generate formal code review documentation for a feature diff?▼

Generate formal code review documentation by running a structured review on your feature diff to produce an auditable report with reproducible outputs and severity-based findings.

What is a structured code review workflow for post-implementation validation?▼

Structured code review workflows provide independent validation of actual code changes after implementation, enforcing review scope and generating formal documents with severity-based findings.

Can I integrate severity-based code review reports into CI/CD processes?▼

Yes, integrate code review reports into CI/CD processes and project documentation, as the structured output supports automated quality assurance and auditability checks.

Does independent code diff analysis work for both beads and features?▼

Yes, independent code diff analysis applies to both beads and features, using structured post-implementation review scenarios to ensure independent validation across development scopes.

What's the best way to ensure code review findings are auditable?▼

Ensure code review findings are auditable by enforcing review scope and reproducible outputs, generating a formally structured report with severity-based findings for quality assurance.

When should I use a formal code review report instead of informal feedback?▼

Use a formal code review report when you need independent validation and auditable findings for post-implementation quality assurance, rather than informal feedback during early planning phases.