code-review

Review specified files for architecture, quality, and ADR compliance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents costly rework by performing a structured review that detects architectural violations, quality regressions, and testability or performance risks before code is merged or shipped.

Core Features & Use Cases

  • Targeted, file-based reviews: Review one file or a set of files and produce a consistent verdict.
  • ADR compliance checking: Detect deviation from the governing Architectural Decision Records (ADRs) by optionally using a provided story path or scanning implementation headers and commit messages.
  • Standards, SOLID, and game-specific checks: Validate documentation, method size/complexity, dependency direction, layer separation, cleanup, and runtime concerns relevant to gameplay code.

Quick Start

Run code-review on a directory of Lua files you plan to integrate, for example: /code-review path/to/src.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I detect architectural drift and ADR violations in my codebase?

Run an architectural code review on specific files to detect ADR compliance violations by scanning implementation headers and commit messages. It identifies dependency direction and layer separation issues, outputting a structured verdict with required changes.

What is the best way to enforce SOLID principles and quality standards during code review?

Enforce SOLID principles by running targeted code reviews that validate method complexity, size, and dependency direction. This process checks engine and gameplay code against quality standards to prevent regressions and produce a structured change verdict.

How do I assess testability and performance risks in gameplay code?

Assess testability and performance risks by executing a file-based code review on gameplay code. It evaluates runtime concerns and lifecycle management, returning a structured verdict that highlights required changes to maintain code quality.

Can I run a code review on a directory of Lua files for integration?

Yes, you can run a code review on a directory of Lua files by specifying the target path. The review performs architectural and quality checks to reduce defects and verify ADR compliance before code integration.

When do I need to run an architectural code review?

Run an architectural code review before merging or shipping code to prevent costly rework. Use it to detect quality regressions, SOLID violations, and testability risks across engine, gameplay, UI, and integration workflows.