code-review

Review code changes against coding standards and project specifications.

Updated Jan 29, 2026

Search Tags:#code review #code analysis #coding standards #parallel execution #specification compliance

Ready to run

npx skills add https://github.com/nkabbara/dotfiles --skill code-review-nkabbara

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/nkabbara/dotfiles/tree/main/exact_dot_agents/exact_skills/exact_mattpocock/exact_code-review
Command: npx skills add https://github.com/nkabbara/dotfiles --skill code-review-nkabbara

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code changes against both coding standards and the specifications they should meet, streamlining the code review process.

Core Features & Use Cases

Parallel Review Axes: Simultaneously reviews code for adherence to coding standards and for conformance with specifications.
Automated Comparison: Compares the changes against a specified fixed point (commit, branch, tag, etc.) and identifies deviations.
Sub-agent Execution: Utilizes parallel sub-agents to maintain separation of concerns and prevent context pollution.
Speculative Generality Check: Ensures the code is not speculative or overly general, adhering strictly to the required specifications.

Quick Start

To initiate a review, use the command: /code-review since <fixed-point>.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I automate code review for specification compliance and coding standards?▼

Automate code review by running parallel sub-agents that evaluate specification compliance and coding standards simultaneously, identifying deviations from a fixed point like a commit or branch.

How do I review code changes since a specific commit or branch tag?▼

Review code changes since a specific commit or branch tag by executing the review command with the fixed-point parameter, which compares current code against that baseline for deviations.

What is the best way to check if code changes are overly speculative or general?▼

Check speculative generality by running a specification compliance review that ensures code adheres strictly to required specifications and avoids overly general implementations.

Does parallel code review prevent context pollution when checking multiple standards?▼

Parallel code review prevents context pollution by utilizing separate sub-agents for standards and specification checks, maintaining clear separation of concerns during analysis.

Can I review code changes against both coding standards and project specifications at the same time?▼

Review code changes against both coding standards and project specifications simultaneously by using parallel sub-agents that maintain separation of concerns while analyzing both axes.

What inputs are supported for comparing code changes during a specification compliance review?▼

Specification compliance review supports commits, branches, and tags as input fixed-points for comparing code changes and identifying deviations from documented standards.