code-review

Audit code changes for architecture, security, conventions, and quality using defined checklists and CI/CD gates.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dominikpalatynski/test-ready-app --skill code-review-dominikpalatynski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/dominikpalatynski/test-ready-app/tree/main/.ai/skills/code-review
Command: npx skills add https://github.com/dominikpalatynski/test-ready-app --skill code-review-dominikpalatynski

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Auditors and engineers save time by systematically reviewing code changes for architectural integrity, security, coding conventions, and overall quality.

Core Features & Use Cases

  • Identify changed files and classify by layer (entity, API route, validator, backend page, subscriber, worker, command, widget).
  • Gather context from AGENTS.md for module conventions, read .ai/specs for active specs, and consult .ai/lessons.md for common pitfalls.
  • Enforce standards via a mandatory CI/CD gate sequence: yarn generate, yarn typecheck, yarn test, and yarn build, producing a conformance report.
  • Use references/review-checklist.md as the official checklist for violations, severity, and fixes.
  • Cross-module impact checks: verify event contracts, extension behavior, and widget consumers are unaffected.

Quick Start

Review a pull request by applying the workflow to produce a structured review report.

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 pull requests to check architecture and security?

Automate code review by auditing changes against module conventions, security standards, and architecture layers, then producing a structured conformance report to ensure quality and compliance during pull requests.

What is the best way to enforce coding conventions and CI/CD gates across modules?

Enforce coding conventions by applying a mandatory CI/CD gate sequence—generate, typecheck, test, and build—to verify cross-module impact and ensure event contracts, extension behaviors, and widget consumers remain unaffected.

Does this code review process work with AGENTS.md and custom spec files?

Yes, the code review process reads AGENTS.md for module conventions, checks .ai/specs for active specifications, and consults .ai/lessons.md to identify common pitfalls and ensure compliance throughout the audit.

How do I classify changed files by layer during a code audit?

Classify changed files by layer—entity, API route, validator, backend page, subscriber, worker, command, or widget—to verify architectural integrity and ensure each module adheres to its designated structural role.

Can I use a review checklist to identify violations and severity during code audits?

Yes, you can use references/review-checklist.md as the official checklist to identify violations, determine severity levels, and apply fixes, ensuring consistent quality standards across all code changes.