← ClaudeAtlas

code-qualitylisted

Review a change across correctness, readability, architecture, security and performance, with severity-labelled findings and structural remedies rather than complaints. Use before merging anything, after finishing a feature, when evaluating code written by another agent or model, after a bug fix, when refactoring, or when asked to review a diff, a branch or a PR.
Udhay-Adithya/skills · ★ 0 · Code & Development · score 70
Install: claude install-skill Udhay-Adithya/skills
# Code quality Review every change before it merges. Five axes, findings labelled by what they require, and a named remedy attached to anything structural. **The standard for approval:** approve a change that definitely improves overall code health, even where it is not perfect. Perfect code does not exist and the goal is continuous improvement. Do not block something because it is not how you would have written it. If it improves the codebase and follows the project's conventions, approve it. ## The five axes ### 1. Correctness - Does it match the spec or the task? - Are the edge cases handled: null, empty, zero, the boundary, the maximum? - Are the error paths handled, not only the happy one? - Do the tests pass, and are they testing the right thing? - Any off-by-one, any race, any state that can go inconsistent? ### 2. Readability - Are the names descriptive and consistent with the project? No bare `data`, `temp`, `result`. - Is the control flow followable, without nested ternaries or deep callbacks? - **Could this be shorter?** A thousand lines where a hundred would do is a failure, not thoroughness. - **Is each abstraction earning its complexity?** Do not generalise before the third case. - Is there dead code: unused variables, compatibility shims, commented-out blocks? - **Is a new conditional bolted onto an unrelated flow?** That is a design smell, not a nit. Push the logic into its own helper or state instead of tangling a path that already works. - **D