code-review

Review implementation files for architectural, ADR, SOLID, and domain-specific defects.

18|5|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill code-review-wsman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill code-review-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams perform consistent post-implementation code reviews so architectural problems, quality regressions, and domain-specific risks are caught before changes are accepted.

Core Features & Use Cases

  • Architecture and Standards Review: Evaluates dependency direction, layer separation, complexity, documentation, and dependency injection across the implementation.
  • ADR and SOLID Checks: Compares the change against referenced architecture decisions and flags violations, drift, or minor deviations.
  • Domain-Specific Validation: Reviews product or game concerns such as API boundaries, schema safety, auth, observability, frame timing, resource cleanup, and testability.
  • Use Case: After a story is implemented, run this Skill on the touched files to get a structured verdict with positive observations, required changes, and suggestions.

Quick Start

Use the code-review skill on the target path to evaluate the implementation and return a read-only architectural review with findings and verdict.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I run an architecture and SOLID compliance code review after implementation?

To run an architecture and SOLID compliance code review, target the implemented files for full-file inspection. The review cross-checks ADRs, evaluates dependency direction and layer separation, then returns a read-only verdict with required changes and suggestions.

What does a post-implementation code review check for domain-specific defects?

A post-implementation code review checks domain-specific defects by validating API boundaries, schema safety, auth, observability, frame timing, resource cleanup, and testability to ensure product and game story implementations meet quality standards.

How do I validate ADR compliance and check for architecture drift before merge?

Validate ADR compliance by comparing implementation changes against referenced architecture decisions. This process flags violations, drift, and minor deviations to catch architectural problems and quality regressions before changes are accepted.

Can I use automated code review for game story implementation files?

Yes, automated code review supports game story implementation files by evaluating frame timing, resource cleanup, and testability. It performs read-only reporting on target files and modules requiring post-implementation QA validation.

What is the best way to catch architecture issues and quality regressions before merge?

The best way to catch architecture issues is performing consistent post-implementation reviews that evaluate dependency injection, complexity, and layer separation. This structured review returns positive observations, required changes, and suggestions.

What are the limitations of read-only code review for QA validation?

Read-only code review limitations include no direct code modifications; it only provides reporting with verdicts and suggestions. It requires full-file inspection and specialist review coordination to identify architectural and standards defects.