codereview-style

Enforce code style, naming, structure, and documentation standards across repositories.

8|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/xinbenlv/codereview-skills --skill codereview-style
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codereview-style
Source: https://github.com/xinbenlv/codereview-skills/tree/main/skills/codereview-style
Command: npx skills add https://github.com/xinbenlv/codereview-skills --skill codereview-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams enforce code quality by performing automated checks on readability, naming consistency, modularity, abstractions, and documentation accuracy, reducing review cycle time and preventing maintainability issues.

Core Features & Use Cases

  • Readability: verify meaningful names, formatting, and clear logic.
  • Modularity & Abstractions: ensure single responsibility and proper boundaries.
  • Documentation quality: check inline docs and external docs for accuracy.
  • Use Case: During PR reviews, pre-merge checks, or onboarding to surface style and maintainability issues quickly.

Quick Start

Run codereview-style on the target codebase to perform a final pass for readability, naming, modularity, and documentation checks and return concrete improvements.

Frequently Asked Questions about codereview-style

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

FAQPage Schema
How do I automate code review checks for readability and naming conventions?

Automate code review checks by running a final quality pass that verifies readability, enforces naming conventions, and surfaces concrete improvements to reduce review cycle time and ensure maintainability.

What is the best way to enforce modularity and abstraction boundaries in a pull request?

Enforce modularity by applying automated structure checks during PR reviews to ensure single responsibility and proper abstraction boundaries, preventing maintainability issues before merging code.

Can I check documentation accuracy automatically during a pre-merge check?

Yes, you can check documentation accuracy during pre-merge checks by verifying inline docs and external docs against code changes to maintain documentation quality and accuracy.

Does this automated style check work across multiple programming languages?

Yes, the automated style check applies to software repositories across languages, verifying structure, naming, and documentation standards to ensure maintainability during code reviews.

Why do I need a final quality pass for code style and maintainability?

A final quality pass for code style is needed to enforce readability, modularity, and documentation standards, reducing manual review effort and preventing long-term maintainability issues.