style-audit
Installation
SKILL.md
Style Audit
Review code quality consistency, coding patterns, and style drift.
Scope
1. Naming and shape consistency
- naming consistency across types, constants, functions, and files
- factory naming (
create*for factories; avoidbuild*/make*unless established locally) - export shape: prefer direct
export constover local alias +export { ... } - import clarity: avoid aliasing unless it resolves a collision
- module layout consistency
2. Control flow and state modeling
- switch exhaustiveness (
default+unreachablewhen applicable) - assert patterns (
invariantfor impossible states vs user-facing errors) - prefer explicit status/state fields over boolean flags for lifecycle phases
Related skills
More from cniska/skills
tdd
Drive implementation with red-green-refactor. Use when building features or fixing bugs test-first.
12review
Run all review skills against the current branch diff. Use when reviewing a feature branch before merge.
10plan
Design a feature or behavior change through dialogue. Use when asked to plan, scope, design, or break down work before coding.
10explore
Explore a task or design through systematic questions until reaching shared understanding. Use before implementing complex or ambiguous work.
10issue
Create a GitHub issue from a short description. Use when filing a bug, feature request, or task.
10pr
Create a pull request with review and verify. Use when the branch is ready to merge.
10