code-review

Reviews source files against coding standards, architecture rules, and SOLID principles.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/onemanking/the-operator --skill code-review-onemanking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/code-review
Command: npx skills add https://github.com/onemanking/the-operator --skill code-review-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually reviewing code for standards compliance, architectural violations, and SOLID principle adherence is time-consuming and inconsistent. This Skill provides a structured, repeatable review process that evaluates files against project coding standards and outputs a standardized verdict. ## Core Features & Use Cases - Standards Compliance Checks: Verifies doc comments, cyclomatic complexity under 10, method length limits, dependency injection, and interface exposure. - Architecture and SOLID Analysis: Checks dependency direction, circular dependencies, layer separation, and all five SOLID principles. - Game Development Checks: Flags frame-rate dependence, allocations in hot paths, null handling, thread safety, and resource leaks. - Use Case: After implementing a new gameplay system in a Phaser/React project, invoke the review on the changed files to receive a structured report with a verdict of APPROVED, APPROVED WITH SUGGESTIONS, or CHANGES REQUIRED before merging. ## Quick Start Ask the assistant to run a code review on a specific file or directory, for example: review the file src/game/systems/InferenceSystem.ts for standards and architecture compliance.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I run a code review on a specific file?

Invoke the code-review skill with the path to the target file or directory as the argument. The skill reads the files in full, loads the project coding standards from CLAUDE.md, and outputs a structured review report with a final verdict.

What coding standards does an automated code review check?

This review checks doc comments on public methods, cyclomatic complexity under 10 per method, method length under 40 lines, dependency injection instead of static singletons, configuration loaded from data files, and interface-based system exposure.

Does the code review check SOLID principles?

Yes, the review evaluates all five SOLID principles: Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion. Violations are listed specifically in the SOLID section of the report.

Can the review detect game development performance issues?

Yes, it checks for frame-rate independence through delta time usage, memory allocations inside update loops, null and empty state handling, thread safety where required, and proper resource cleanup to prevent leaks.

What output format does the code review produce?

The review outputs a structured Markdown report with sections for standards compliance score, architecture assessment, SOLID compliance, game-specific concerns, positive observations, required changes, suggestions, and a final verdict of APPROVED, APPROVED WITH SUGGESTIONS, or CHANGES REQUIRED.