review-review

Review changed files for architecture, types, security, and test coverage.

20|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/HerbertJulio/specialist-agent --skill review-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-review
Source: https://github.com/HerbertJulio/specialist-agent/tree/main/packs/svelte/skills/review-review
Command: npx skills add https://github.com/HerbertJulio/specialist-agent --skill review-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code changes often introduce architectural mismatches, type errors, security gaps, or insufficient tests. A structured review ensures changes align with project guidelines and quality standards to prevent regressions before merge.

Core Features & Use Cases

  • Comprehensive architecture, type, and security review of changed files.
  • Enforcement of coding standards, test coverage, and runtime safety checks.
  • Clear, actionable recommendations and a consistent merge-ready verdict.

Quick Start

Review the latest changes in the current branch and generate a structured compliance report.

Frequently Asked Questions about review-review

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

FAQPage Schema
How do I automate code review for architecture, types, and security before merging?

Automate code review by validating architecture, types, security, and test coverage for changed files. It retrieves the git diff and runs checks to enforce coding standards and generate a final compliance verdict.

What's the best way to validate test coverage and security on active branch changes?

Validate test coverage and security by applying a structured review process to files changed in your active branch or staged changes. It ensures changes align with project guidelines and quality standards to prevent regressions.

Does code review adapt to various repo setups and different tech stacks?

Yes, code review adapts to various repo setups and stacks. It evaluates the changed files regardless of the specific environment to enforce runtime safety checks and coding standards consistently.

How do I check for type errors and linting issues in staged changes?

Check for type errors and linting issues by reviewing staged changes with integrated type check and linting runs. This process identifies mismatches and enforces type safety before generating a merge-ready verdict.

Can I get a merge-ready compliance report for my latest code changes?

Yes, you can generate a structured compliance report for your latest changes. The review process provides clear, actionable recommendations and a consistent merge-ready verdict based on architecture, type, and security checks.