review

Name: review
Availability: InStock
Author: Kartik

Review code diffs against documented standards and originating specifications.

Updated Jul 17, 2026

Search Tags:#diff analysis #code review #pull request #standards #spec compliance #branch review

Ready to run

npx skills add https://github.com/kartikkabadi/skills --skill review-kartikkabadi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/kartikkabadi/skills/tree/main/review
Command: npx skills add https://github.com/kartikkabadi/skills --skill review-kartikkabadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review a code change against both the repository’s standards and the originating spec, so you can catch style issues and requirement gaps in one pass.

Core Features & Use Cases

Two-axis review: Checks the diff for both coding-standard violations and spec mismatches.
Parallel analysis: Runs standards and spec reviews separately so findings stay cleanly separated.
Use case: Use it when reviewing a branch, pull request, or work-in-progress changes and you need a structured assessment of correctness and quality.

Quick Start

Review the changes since main and compare them against the relevant spec.

Frequently Asked Questions about review

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

FAQPage Schema

How do I review a code diff against project standards and spec compliance?▼

To review a code diff against standards and spec compliance, you need a fixed comparison point, standards source files, and a spec source to identify missing requirements, scope creep, and standard violations.

Can I check a pull request for both coding standard violations and spec mismatches in one pass?▼

Yes, you can check a pull request for coding standard violations and spec mismatches simultaneously by running parallel analysis that keeps standards findings and spec requirement gaps cleanly separated.

What is the best way to assess work-in-progress changes for scope creep and missing requirements?▼

Assessing work-in-progress changes for scope creep and missing requirements requires comparing the diff against a fixed branch point and the originating specification to ensure correctness and quality.

How does branch review work when checking for documented coding conventions?▼

Branch review works by comparing branch changes against documented standards source files and the originating specification, applying a two-axis review to catch style issues and requirement gaps.

Do I need a fixed comparison point to review commits for spec compliance?▼

Yes, you need a fixed comparison point to review commits for spec compliance, along with standards source files and a spec source, to accurately report missing requirements and standard violations.