Menu
Use when writing, fixing, editing, or refactoring TypeScript, Python, React, or CSS code. Not for PR or diff reviews — use clean-code-reviewer for those.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when checking code for functional correctness, backwards compatibility, logic errors, security vulnerabilities, performance issues, or missing test coverage — not style.
Use when reviewing code, pull requests, branches, diffs, or changed files for quality, correctness, security, performance, and style issues.
Use when writing, fixing, or editing comments or documentation in any language, especially commented-out code, stale docs, metadata comments, TODO banners, redundant comments, or unclear comment value.
Use when naming or renaming identifiers in any language, especially cryptic names, ambiguous parameters, type or scope encodings, misleading side effects, or requests for clearer names.
Use when writing, fixing, or editing code in any language with duplicated logic, magic values, unclear one-liners, mixed responsibilities, clutter, arbitrary code, or inconsistent abstraction levels.
Use when writing, fixing, or editing Python async flows, coroutines, asyncio tasks, retries, timeouts, cancellation, shared mutable state across awaits, race conditions, or flaky async tests.
| name | clean-code |
| description | Use when writing, fixing, editing, or refactoring TypeScript, Python, React, or CSS code. Not for PR or diff reviews — use clean-code-reviewer for those. |
Use this as the top-level entry point for the clean-code skill collection. It should activate the relevant track skills for the files and concerns in front of you, then report findings with the specialized rule IDs.
| Work | Use |
|---|---|
| Broad TypeScript quality, functions, modules, async flows, boundaries, data modeling, errors, tests | clean-typescript plus clean-general, clean-general-names, and clean-general-comments |
| Broad Python quality, functions, modules, async flows, boundaries, data modeling, errors, tests | clean-python plus clean-general, clean-general-names, and clean-general-comments |
| React components, JSX, hooks, effects, state, React tests, file ownership | clean-react plus clean-typescript, clean-general, clean-general-names, and clean-general-comments |
| CSS, CSS Modules, CSS-in-JS, Tailwind classes, inline styles, tokens, layout, visual accessibility | clean-css |
When editing code with clean-code expectations:
Do not treat clean-code as a replacement for the specialized skills. It is a router.
For broad edits, include every relevant track instead of choosing only one. For example, a .tsx component with CSS Modules should use clean-typescript, clean-react, clean-css, and the general skills. A Python API handler should use clean-python and the general skills.
