code-reviewer

Name: code-reviewer
Availability: InStock
Author: buiphucminhtam

Identify architecture conformance, anti-patterns, and code quality risks without modifying source files.

47|11|Updated Mar 6, 2026

Search Tags:#architecture #quality #code-quality #static-analysis #code-review #review-tool

Ready to run

npx skills add https://github.com/buiphucminhtam/forgewright --skill code-reviewer-buiphucminhtam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/buiphucminhtam/forgewright/tree/main/skills/code-reviewer
Command: npx skills add https://github.com/buiphucminhtam/forgewright --skill code-reviewer-buiphucminhtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and surface architecture conformance issues, anti-patterns, and maintainability risks in codebases without modifying source.

Core Features & Use Cases

Spec-compliant review: Verifies alignment with architecture decisions, ADRs and OpenAPI/OpenAPI-like contracts.
Two-stage review: First confirm spec compliance, then assess code quality across SOLID, DRY, error handling, logging, and maintainability.
Output artifacts: Generates structured findings and writes reports to the designated .forgewright/code-reviewer/ directory.

Quick Start

Run a read-only code review against a repository to surface architectural and quality findings.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema

How do I check architecture conformance against ADRs in a codebase?▼

Architecture conformance is checked by verifying codebase alignment with architecture decisions, ADRs, and OpenAPI contracts. The review identifies anti-patterns and maintainability risks without modifying source files, outputting structured findings to the .forgewright/code-reviewer/ directory.

What is the best way to automate spec compliance and code quality reviews?▼

Automated spec compliance and code quality reviews use a two-stage process: first verifying alignment with BRD/PRD criteria and architecture decisions, then assessing SOLID, DRY, error handling, logging, and maintainability to surface production-grade validation issues early.

How does a two-stage code review process work for backend services and frontend apps?▼

A two-stage code review process works by first confirming spec compliance against architecture decisions and contracts, then evaluating code quality across SOLID, DRY, error handling, and logging for backend services, frontend apps, and libraries.

Can I run a read-only code review without modifying my source files?▼

Read-only code review can run against a repository without modifying source files. It surfaces architectural and quality findings by applying production-grade validation to backend services, frontend apps, and libraries, writing structured artifacts to .forgewright/code-reviewer/.

Does static analysis for code quality enforce BRD and PRD criteria?▼

Static analysis for code quality enforces BRD/PRD criteria by applying a spec compliance check followed by a code quality review. It validates alignment with these requirements and surfaces architecture conformance issues and anti-patterns early in the development cycle.

What limitations exist when reviewing code quality without modifying source?▼

Reviewing code quality without modifying source is limited to identifying and reporting architecture conformance issues and maintainability risks. It generates structured artifacts and reports but does not fix or rewrite the detected anti-patterns in the codebase.