Menu
Review code style, naming, patterns, and consistency. Use when reviewing code quality or style drift.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | style-review |
| description | Review code style, naming, patterns, and consistency. Use when reviewing code quality or style drift. |
Review naming, coding patterns, and style consistency against the codebase's existing conventions.
Check where the codebase already has a clear local pattern:
Sections 1 and 3 require evidence of a local convention — cite the nearby code that establishes it. Sections 2 and 4 are default checks that apply without repo evidence, but cap them at Consider unless a documented convention elevates them. Never report a default check as must-fix.
For each finding: label (Critical / Fix / Consider / Nit — see review), file, violated convention, evidence (cite both the offending line and the code that establishes the convention), fix direction.
getUserData — inconsistent, should be fetchUserData." (no evidence)src/api/user.ts:12 getUserData breaks the fetch-prefix convention (9 of 10 siblings in src/api/ use fetch*). Rename to fetchUserData.Order Critical → Fix → Consider → Nit. If nothing clears the threshold, report "No style findings" — don't pad.
Create and update AGENTS.md project rules. Use when authoring or amending the cross-tool conventions agents must follow.
Write forward-looking startup instructions for the next session, then reset context to save costs. Use when the context is getting long or before switching focus.
Run pre-release checks, pick the version bump, and cut the release. Use when ready to tag and release.
Create and maintain a specification that states what to build, not how. Use when writing a spec, editing requirements, or defining acceptance criteria.
Run all review dimensions against a diff or a path. Use when reviewing a feature branch before merge, reviewing someone else's PR, or auditing a file path.
Create or update project documentation. Use when creating architecture docs, runtime docs, reference docs, or design documents that explain what the system does.