code-review-patterns

Enforce spec compliance before quality review in code submissions.

161|25|Updated Oct 22, 2025

Search Tags:#performance #security #maintainability #QA #code-review #spec-compliance

Ready to run

npx skills add https://github.com/romiluz13/cc10x --skill code-review-patterns-romiluz13

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-patterns
Source: https://github.com/romiluz13/cc10x/tree/main/plugins/cc10x/skills/code-review-patterns
Command: npx skills add https://github.com/romiluz13/cc10x --skill code-review-patterns-romiluz13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures code reviews verify functionality against the spec before addressing quality attributes like security, performance, and maintainability.

Core Features & Use Cases

Stage 1: Spec Compliance Review: Verify behavior against requirements and edge cases.
Stage 2: Code Quality Review: Assess security, correctness, performance, maintainability, and UX.
Security Checklist: Review for input validation, authentication/authorization, secrets, and more.

Quick Start

Run Stage 1 to verify spec compliance; if it passes, proceed to Stage 2 and address security issues found.

Frequently Asked Questions about code-review-patterns

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

FAQPage Schema

How do I structure code reviews to check spec compliance before quality assessment?▼

Two-stage code review enforces spec compliance verification first, then quality assessment. Stage 1 validates behavior against requirements and edge cases; Stage 2 applies security, performance, and maintainability checklists only after Stage 1 passes, ensuring traceable, requirement-driven evaluation.

What should I check during the spec compliance stage of a code review?▼

Stage 1 spec compliance review verifies that code submissions meet functional requirements, handle edge cases correctly, include adequate tests, and align with the specification. This gates progression to quality assessment and prevents quality reviews from proceeding on non-compliant code.

What security issues should a code review checklist cover?▼

Security review focuses on input validation, authentication and authorization mechanisms, secrets management, and other vulnerabilities. This checklist runs as part of Stage 2 quality assessment after spec compliance passes, ensuring security flaws don't block functional verification.

Can I use this two-stage approach for pull requests and patches?▼

Yes, two-stage review applies across code submissions including pull requests and patches. The spec-first methodology gates Stage 2 quality checks on Stage 1 compliance success, maintaining consistent evaluation regardless of submission type.

Why should spec compliance come before quality review?▼

Verifying spec compliance first prevents quality reviewers from assessing maintainability, performance, or security on code that doesn't meet requirements. This sequencing ensures functional correctness precedes optimization, reducing rework and focusing review effort efficiently.

What quality dimensions does Stage 2 cover beyond security?▼

Stage 2 quality review assesses correctness, performance, maintainability, user experience, and accessibility alongside security. These attributes are evaluated only after Stage 1 spec compliance passes, ensuring comprehensive quality across all dimensions.