pragmatic-clean-code-reviewer

Automate rule-based code reviews with citations from classic software engineering books.

213|19|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/Zhen-Bo/pragmatic-clean-code-reviewer --skill pragmatic-clean-code-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pragmatic-clean-code-reviewer
Source: https://github.com/Zhen-Bo/pragmatic-clean-code-reviewer/tree/main
Command: npx skills add https://github.com/Zhen-Bo/pragmatic-clean-code-reviewer --skill pragmatic-clean-code-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill automates rule-based code reviews against classic software engineering books.

Core Features & Use Cases

  • 3+4+2 questionnaire-driven strictness mapping (L1-L5)
  • Standardized reports with rule citations across PP/CC/CA
  • Language-aware adjustments for multi-language codebases
  • On-demand references and asset/document support

Quick Start

Invoke the skill with /pragmatic-clean-code-reviewer to start a code-review session.

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 automate code reviews based on classic software engineering rules?

You can automate rule-based code reviews by applying a 15-point checklist with rule citations from classic software engineering books. This generates standardized reports to enable actionable fixes across your organization's codebase.

How does static analysis handle multi-language codebases during a code review?

Static analysis for code reviews handles multi-language codebases by applying language-aware adjustments. This ensures the 15-point checklist and rule citations remain accurate and standardized across different programming languages and teams.

Can I enforce different levels of strictness for code quality assurance across my teams?

Yes, you can enforce code quality assurance strictness using a 3+4+2 questionnaire-driven mapping model. This maps to L1-L5 strictness levels to accommodate varying project requirements and organizational standards.

What's the best way to generate standardized code review reports with rule citations?

The best way to generate standardized code review reports is to automate rule-based reviews against classic software engineering principles. This process outputs actionable fixes categorized across PP, CC, and CA dimensions with explicit rule citations.

Does this code review approach support organization-wide architecture and quality assurance standards?

Yes, this rule-based code review approach targets organization-wide codebases across various languages and teams. It enforces a strict 15-point checklist to ensure uniform quality assurance and architecture standards throughout the organization.