code-review

Review code changes across three sequential stages for spec compliance and quality.

Updated Jul 1, 2026

Search Tags:#code quality #code review #pull request #software development #spec compliance #domain integrity

Ready to run

npx skills add https://github.com/jwilger/eventcore --skill code-review-jwilger

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of ensuring code quality, spec compliance, and domain integrity by providing a structured, multi-stage review process that prevents issues from being overlooked.

Core Features & Use Cases

Three-Stage Review: Separates spec compliance, code quality, and domain integrity into distinct, sequential passes.
Focused Evaluation: Ensures each aspect of the code receives dedicated attention, preventing thoroughness in one area from compromising another.
Use Case: When preparing a Pull Request, activate this Skill to systematically check if the code meets all requirements, adheres to quality standards, and respects domain boundaries before merging.

Quick Start

Use the code-review skill to review the attached code changes for spec compliance and quality.

Frequently Asked Questions about code-review

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

FAQPage Schema

What is a systematic code review process for pull requests?▼

A systematic code review process evaluates code changes in sequential stages, separating spec compliance, code quality, and domain integrity into distinct passes to ensure focused assessment before merging.

How do I check code changes for spec compliance and domain integrity?▼

You check spec compliance and domain integrity by applying a multi-stage review protocol that first verifies requirements, then assesses code quality, and finally validates domain boundaries through structured feedback categorization.

What's the best way to structure code review feedback for software development?▼

The best way to structure code review feedback is through categorized evaluation across three sequential stages, ensuring spec compliance, quality standards, and domain integrity are assessed separately without thoroughness in one area compromising another.

Can I use a multi-stage code review for preparing any pull request?▼

Yes, you can use a multi-stage code review for preparing any pull request. It applies to software development workflows for assessing code changes and ensuring implementation quality against requirements before merging.

Why separate spec compliance from code quality during a code review?▼

Separating spec compliance from code quality prevents issues from being overlooked by ensuring each aspect receives dedicated attention, stopping thoroughness in one area from compromising evaluation in another.