review

Evaluate software feature implementations against architectural and design standards.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/nazrulsoftwaredev/NIT_CRM_2 --skill review-nazrulsoftwaredev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/nazrulsoftwaredev/NIT_CRM_2/tree/main/.agents/skills/review
Command: npx skills add https://github.com/nazrulsoftwaredev/NIT_CRM_2 --skill review-nazrulsoftwaredev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common issue of feature drift, where code works on the surface but violates architectural boundaries, design standards, or misses critical edge cases.

Core Features & Use Cases

  • Three-Layer Verification: Systematically checks plan alignment, system integrity, and production readiness.
  • Severity-Based Reporting: Categorizes findings into Critical, Important, and Minor to help developers prioritize fixes.
  • Use Case: After completing a new user authentication module, run this skill to ensure the implementation adheres to the project's security architecture and handles all edge cases like network timeouts or invalid inputs.

Quick Start

Run the review skill to evaluate the current feature implementation against the project architecture and design standards.

Frequently Asked Questions about review

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

FAQPage Schema
How do I check if my new feature implementation aligns with the project architecture?

To check feature implementation alignment, evaluate the codebase against predefined architectural plans and system constraints. This verifies technical consistency by flagging architectural violations and design system drift.

What is the best way to verify production readiness and error handling in software development?

Production readiness verification involves checking the codebase against established system constraints to identify missing error handling. This ensures reliability by catching unhandled network timeouts or invalid inputs before deployment.

How do I systematically review code for architectural violations and design drift?

Systematic code review uses a three-layer verification process checking plan alignment, system integrity, and production readiness. It categorizes findings by severity into Critical, Important, and Minor to prioritize fixes.

Can I use an automated review process to detect feature drift in my codebase?

Yes, you can detect feature drift by comparing current codebases against established project plans. This identifies deviations where code works on the surface but violates architectural boundaries or design standards.

How do I prioritize fixes when a code review finds multiple architectural and design issues?

Prioritize code review fixes using severity-based reporting that categorizes findings into Critical, Important, and Minor. This helps developers address architectural violations and missing error handling systematically.