style-reviewer

Check code against project linter conventions for naming, formatting, and structure.

Updated Mar 26, 2026

Search Tags:#formatting #style #conventions #imports #lint #code-review #naming

Ready to run

npx skills add https://github.com/benediktms/overmind --skill style-reviewer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: style-reviewer
Source: https://github.com/benediktms/overmind/tree/main/cli/claudecode-plugin/skills/style-reviewer
Command: npx skills add https://github.com/benediktms/overmind --skill style-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Checks code for consistency with project conventions — naming, formatting, import order, file organization, comment style. Use when a change needs convention-focused review before merge, lint findings need interpretation, or naming and formatting drift must be corrected. Not for bug triage, security analysis, performance profiling, or any task where no established project conventions exist to anchor findings.

Core Features & Use Cases

Reference project conventions from linter config and existing code to drive checks.
Flag only deviations from established local patterns and propose autoformat suggestions.
Batch similar findings for efficient remediation and clear handoff to developers.

Quick Start

Review the latest commit for style and naming drift and apply suggested fixes.

Frequently Asked Questions about style-reviewer

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

FAQPage Schema

How do I enforce naming and formatting conventions during code review?▼

Code review convention checks flag deviations in naming, formatting, and import order by verifying changes against your project's linter configuration and existing code patterns, providing precise, fixable style findings with recommended changes.

Can I use this to check import order and structure across my codebase?▼

You can check import order and structure across your codebase by applying verification against the project's linter configuration during automated CI checks to report precise, fixable style findings with recommended changes.

What's the best way to batch similar lint findings for remediation?▼

Batch similar lint findings for remediation by grouping matching style deviations together during the convention-focused review process, ensuring efficient remediation and clear handoff to developers for fixing naming and formatting drift.

Do I need an existing linter configuration to anchor style checks?▼

An existing linter configuration is required to anchor style checks because this process is not intended for contexts where no established project conventions exist to drive naming, formatting, and organization validation.

When should I not use a convention-focused style review?▼

Avoid convention-focused style review for bug triage, security analysis, performance profiling, or any task where no established project conventions exist to anchor findings and drive formatting checks.