What problem does it solve?
Standard code formatters only fix whitespace, braces, and basic formatting issues, leaving cross-file and semantic consistency drift undetected. This drift includes mixed naming conventions, inconsistent code patterns, divergent API shapes, and uneven file organization that compounds cognitive load, breaks grep-based refactors, and teaches new contributors that inconsistent practices are acceptable.
Core Features & Use Cases
- Multi-language consistency checking: Validates naming conventions, code patterns, and style rules across 7+ languages including Python, JavaScript/TypeScript, C#, Java, C/C++, Rust, Go, and SQL.
- Drift detection beyond formatters: Catches issues formatters can't see, such as mixed async/await and .then() usage, inconsistent error-handling strategies, divergent API return shapes, and mismatched import ordering semantics.
- Monorepo-wide enforcement: Validates uniform configuration across packages, consistent public API shapes, and aligned version requirements for multi-package repositories.
- Use Case: A team maintaining a TypeScript monorepo can use this skill to identify mixed camelCase and snake_case function names across packages, inconsistent error-handling patterns between public APIs, and divergent formatter configurations that bypass root-level rules.
Quick Start
Use the consistency-checker skill to audit your codebase for naming, pattern, and style inconsistencies across all files and packages.
