review

Automates code quality validation across formatting, tests, coverage, and coding standards.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/julianjab/ia-tools --skill review-julianjab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/julianjab/ia-tools/tree/main/skills/review
Command: npx skills add https://github.com/julianjab/ia-tools --skill review-julianjab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality validation across formatting, tests, coverage, and coding standards to ensure reliable code.

Core Features & Use Cases

  • Format & lint: automatically format code and enforce style.
  • Test & coverage: run unit/integration tests and validate coverage thresholds.
  • Coding standards enforcement: verify adherence to project rules defined in CLAUDE.md.

Quick Start

Run /review in your repository to execute the full quality gate.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code quality checks across a monorepo?

Automate code quality validation by running formatting, tests, coverage, and linting against changed packages or the entire repository. The tool detects project manifests to apply the correct quality gates automatically.

What is the best way to enforce coding standards and coverage thresholds?

Enforce coding standards by validating code against project rules defined in CLAUDE.md. The quality gate runs unit and integration tests to verify coverage thresholds and reports any failures.

Can I auto-correct formatting and linting errors during a code review?

Yes, auto-correction is supported using the --fix flag. This automatically formats code and enforces style rules to resolve formatting and linting errors without manual intervention.

Does this automated code review tool work with multi-stack software projects?

Yes, the code quality validation supports multi-stack software projects. It detects tooling through common manifests and configuration files to run appropriate checks across different stacks.

How are failed tests and coverage gaps handled during validation?

Failed tests and coverage gaps are reported after running the validation suite. The tool can automatically delegate these failures to specialized subagents for targeted resolution.

What should I do if my code quality validation is not detecting the right tooling?

Ensure your tooling is properly configured in CLAUDE.md and common manifests. The validation process relies on these files to detect the correct tools for formatting, testing, and coverage checks.