review

Review code changes against coding standards and specifications.

Updated Jun 6, 2026

Search Tags:#code quality #code review #review process #standards compliance #specification adherence

Ready to run

npx skills add https://github.com/guille-gallo/auth-kit --skill review-guille-gallo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/guille-gallo/auth-kit/tree/main/.agents/skills/review
Command: npx skills add https://github.com/guille-gallo/auth-kit --skill review-guille-gallo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive review of code changes against both coding standards and specifications, ensuring code quality and adherence to requirements.

Core Features & Use Cases

Two-Axis Review: Evaluates code changes against coding standards and specifications in parallel.
Standards Compliance: Checks for adherence to documented coding standards.
Spec Adherence: Ensures code matches the requirements outlined in originating issue/PRD/spec.
Use Case: Ideal for reviewing pull requests, branches, or any code changes to ensure both quality and adherence to specifications.

Quick Start

Run the review skill on the latest commit with the command: 'review -c latest'.

Frequently Asked Questions about review

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

FAQPage Schema

How do I review code changes against both specifications and coding standards?▼

You can review code changes by running parallel checks that evaluate commits against documented coding standards and originating specifications. This dual-axis review requires Git for commit comparison and an issue tracker for spec identification.

What is a specification adherence check in a code review process?▼

A specification adherence check ensures code matches the requirements outlined in the originating issue, PRD, or spec. It runs in parallel with standards compliance checks to validate that code changes fulfill documented requirements.

Do I need Git and an issue tracker to perform standards compliance reviews?▼

Yes, Git is required for commit comparison to isolate code changes, and an issue tracker is needed for spec identification. These dependencies provide the baseline diffs and originating requirements needed for the parallel review process.

How do I check the latest commit for coding standards compliance?▼

You can check the latest commit for standards compliance by running the review command with the latest commit flag. This evaluates the newest changes against documented coding standards and originating specifications in parallel.

What's the best way to ensure pull requests meet documented coding standards?▼

The best way to ensure pull requests meet documented coding standards is running a parallel two-axis review. This checks standards compliance and specification adherence simultaneously, validating both code quality and requirement fulfillment for branch changes.

When should I use a parallel review process instead of a manual code review?▼

A parallel review process should be used when you need to verify both coding standards compliance and specification adherence simultaneously. It is ideal for reviewing pull requests or branches to ensure code quality matches documented rules and originating requirements.