review

Review TypeScript, React, and architecture for quality, security, and correctness issues.

41|3|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/darkroomengineering/cc-settings --skill review-darkroomengineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/darkroomengineering/cc-settings/tree/main/skills/review
Command: npx skills add https://github.com/darkroomengineering/cc-settings --skill review-darkroomengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews are essential to catch defects, security risks, and adherence to Darkroom standards before changes are merged. This skill provides a structured, repeatable review workflow that guides reviewers through TypeScript, React, and architectural checks to improve code quality and long-term maintainability.

Core Features & Use Cases

  • TypeScript checks: ensure no any types, use unknown where appropriate, strict mode, proper interface/type exports, and justified type assertions.
  • React patterns: prefer server components by default, use 'use client' only when needed, leverage proper wrappers for image and links, and avoid unnecessary memoization where the React compiler can optimize.
  • Performance & Security: flag potential N+1 queries, ensure input validation at boundaries, guard against secrets or credentials in code, and avoid unsafe DOM interactions.
  • Architecture & Best Practices: verify correct file placement, clear separation of concerns, and consistent naming conventions across the codebase.
  • Use Case: Prior to merging a PR, run a comprehensive review to surface critical issues and actionable improvements, with suggested fixes.

Quick Start

Initiate a full code review on the latest changes and return a prioritized list of issues.

Frequently Asked Questions about review

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

FAQPage Schema
How do I run a TypeScript code review to catch security and quality issues before merging?

To run a TypeScript code review, apply structured checks to your current changes to identify correctness issues, unsafe type assertions, and potential secrets. This process produces a structured report with critical issues and recommended fixes to ensure strict mode adherence and long-term maintainability.

What React patterns should I check for in a pull request to ensure best practices?

React pattern checks should verify the use of server components by default and restrict 'use client' directives to necessary cases. A code review flags unnecessary memoization and ensures proper wrappers for images and links to align with React compiler optimizations.

How can I identify N+1 query problems and security risks during a code review?

Identify N+1 query problems and security risks by applying performance and security checks to boundary inputs. The review process flags potential N+1 queries, verifies input validation, guards against unsafe DOM interactions, and detects hardcoded credentials.

Does automated code review work for checking architectural concerns like file placement and separation of concerns?

Automated code review works for checking architectural concerns by verifying correct file placement and clear separation of concerns across the repository. It evaluates your codebase against established best practices to surface structural improvements and naming convention inconsistencies.

What is the best way to enforce strict TypeScript rules and eliminate 'any' types in a codebase?

The best way to enforce strict TypeScript rules is to run a code review that actively identifies 'any' types and suggests using 'unknown' where appropriate. This ensures proper interface exports and validates that all type assertions are justified before merging changes.