quality-review

Assess code quality from an integrated git diff and return a structured JSON verdict.

33|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/lvlup-sw/exarchos --skill quality-review-lvlup-sw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-review
Source: https://github.com/lvlup-sw/exarchos/tree/main/skills-src/quality-review
Command: npx skills add https://github.com/lvlup-sw/exarchos --skill quality-review-lvlup-sw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enforce a rigorous, automated stage-2 code quality review that catches SOLID violations, duplication, security issues, and poor test quality before synthesis and merge, preventing low-quality changes from progressing through the workflow.

Core Features & Use Cases

  • Integrated diff review: Operates on orchestrator-provided integrated diffs to evaluate combined branch changes without reading full files.
  • Deterministic gates: Runs static analysis, security scans, and convergence gates (D1–D5) via orchestrate actions and collects structured findings.
  • Test Desiderata & fix loop: Evaluates test quality against explicit desiderata, produces structured JSON verdicts, and manages an automated fix-review loop with escalation rules.
  • Plugin-aware reporting: Merges optional companion plugin findings (axiom, impeccable) and auto-transitions workflow phases based on verdicts.
  • Use case: Run as a subagent to produce a machine-parsable review report that the orchestrator can use to advance or route the feature.

Quick Start

Run a quality review by dispatching the quality-review subagent with the integrated diff and state file after spec review has passed.

Frequently Asked Questions about quality-review

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

FAQPage Schema
How do I automate code review for SOLID violations and security issues in a git diff?

Automated code review evaluates integrated git diffs to catch SOLID violations, security issues, and poor test quality. It applies static analysis and security scans to produce a structured JSON verdict with pass, fail, or blocked outcomes.

What is a D1-D5 convergence gate in static analysis and code review?

A D1-D5 convergence gate is a deterministic check applied during code review to validate multidimensional quality criteria across branch changes. It runs via orchestrate actions to collect structured findings before synthesis and merge.

How do I enforce test quality checks before merging a feature branch?

Test quality enforcement evaluates tests against explicit desiderata using an automated fix-review loop with escalation rules. It produces structured JSON verdicts that determine whether changes can advance through the workflow.

Does code review work without reading full files when evaluating combined branch changes?

Integrated diff review operates exclusively on orchestrator-provided diffs to evaluate combined branch changes without reading full files. It requires an orchestrator-supplied integrated diff and state file to execute its analysis.

Can I merge findings from static analysis and security scans into one report?

Plugin-aware reporting merges optional companion plugin findings from static analysis and security scans into a single machine-parsable report. The orchestrator uses this structured JSON to advance or route the feature automatically.

When should I run a post-spec-review code quality gate?

A post-spec-review code quality gate runs after spec review has passed to enforce rigorous stage-2 checks. It catches duplication, SOLID violations, and security issues before synthesis and merge, preventing low-quality changes from progressing.