pragmatic-clean-code-reviewer

Reviews code changes against Clean Code, Clean Architecture, and Pragmatic Programmer rules with severity-ranked findings.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Coral5644/NekansModPack --skill pragmatic-clean-code-reviewer-coral5644
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pragmatic-clean-code-reviewer
Source: https://github.com/Coral5644/NekansModPack/tree/main/.cursor/skills/pragmatic-clean-code-reviewer
Command: npx skills add https://github.com/Coral5644/NekansModPack --skill pragmatic-clean-code-reviewer-coral5644

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It enforces consistent, principle-based code quality by running a strict L4-level review on every code change, catching correctness bugs, coupling issues, and style violations before they reach production. ## Core Features & Use Cases - 15-Point Review Checklist: Covers correctness, naming, function size, DRY, coupling, error handling, resource cleanup, thread safety, and architecture, each mapped to numbered rules (CC/CA/PP) from three classic software engineering books. - Structured Severity Output: Produces a findings table with severity levels (critical/warning/minor), file and line locations, rule citations, and fix suggestions, plus a pass/fail summary against defined thresholds. - Python 2.7 and NetEase MC Adaptation: Adjusts standard rules for the NetEase Minecraft mod Python 2.7 runtime, including QuMod RPC conventions, main-thread enforcement, and centralized configuration checks. - Use Case: After modifying several game mod modules, ask for a review and receive a rule-cited report flagging a bare except clause, a circular import, and an unbound event listener before commit. ## Quick Start Review my recent code changes using the pragmatic clean code reviewer and report any critical or warning-level issues with fix suggestions.

Frequently Asked Questions about pragmatic-clean-code-reviewer

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

FAQPage Schema
How do I run a code review based on Clean Code principles?▼

Invoke the review after any code modification or before committing large changes. It applies a 15-item checklist covering naming, function size, DRY, error handling, and architecture, returning a severity-ranked table with rule citations and fix suggestions.

What rules does this code review checklist cover?▼

The checklist draws from three books: Clean Code (CC rules on naming, functions, comments, error handling), Clean Architecture (CA rules on SOLID and component coupling), and The Pragmatic Programmer (PP rules on DRY, decoupling, and defensive coding).

Does this code review work with Python 2.7 projects?▼

Yes, it is specifically adapted for Python 2.7 in the NetEase Minecraft mod environment. It checks for Python 3 syntax leaks, type comment conventions, QuMod RPC usage, main-thread API safety, and centralized configuration in Shared/Config.py.

What is the pass/fail threshold for the code review?▼

A changeset passes only with zero critical issues and at most two warnings. Each changeset gets at most two review rounds; remaining non-critical issues after round two become TODO items rather than blockers.

When should I not use strict L4-level code review?▼

Lower the strictness for prototypes or spikes (L2), urgent hotfixes (L3), or temporary debug instrumentation (L1). Reserve L5 for core framework changes where many modules depend on correctness.