code-review

Verify specification compliance before evaluating code quality in pull requests.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill code-review-brunoamsilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/code-review
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill code-review-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that code is correct and meets specifications before spending effort on maintainability and style, preventing wasted review cycles and surfacing critical functional issues early.

Core Features & Use Cases

  • Two-stage review workflow that enforces spec compliance first and only proceeds to code quality once requirements are met.
  • File-by-file, evidence-based feedback with required line numbers, code snippets, explicit fixes, and prioritized recommendations.
  • Use Cases: reviewing pull requests, validating submissions against acceptance criteria, security-focused audits where functional correctness is critical.

Quick Start

Perform a two-stage review of the pull request by checking spec compliance for each file first and then evaluating code quality with line-numbered evidence and prioritized remediation.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I perform a code review that checks spec compliance before code quality?

A two-stage code review verifies specification compliance first and only evaluates code quality once requirements are met. This staged workflow prevents wasted review cycles by surfacing functional issues early before assessing maintainability.

What is the best way to review a multi-file pull request diff with evidence-based feedback?

File-by-file code review analyzes multi-file diffs by producing file-level findings with required line numbers, code snippets, explicit fixes, and prioritized remediation steps. This evidence-based approach ensures actionable feedback for each changed file.

How does a two-stage code review workflow handle specification failures?

A two-stage code review workflow halts quality assessment immediately upon detecting spec failures. By enforcing spec compliance first, it stops reviewers from spending effort on maintainability and style when critical functional requirements are not yet satisfied.

Can I use a spec compliance review for security-focused audits on code submissions?

Spec compliance review suits security-focused audits where functional correctness is critical. Validating code submissions against acceptance criteria ensures that security vulnerabilities stemming from unmet specifications are identified before quality assessment begins.

Why should I check specification compliance before evaluating code quality in a pull request?

Checking specification compliance before code quality ensures correctness and meets requirements before spending effort on maintainability. This staged approach prevents wasted review cycles by surfacing critical functional issues early in the process.

Does a file-by-file code review provide line numbers and code snippets for remediation?

File-by-file code review produces file-level findings with required line numbers, code snippets, explicit fixes, and prioritized remediation steps. This evidence-based feedback ensures developers receive actionable guidance for correcting each file.