Review a change for whether the next person can understand it and change it safely. Use as one lens in a code review run.
55
61%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./code-review/skills/review-maintainability-and-code-quality/SKILL.mdThe canonical home for this skill is tessl/code-review
Review whether the changed code, tests included, can be understood and modified safely without relying on its original author or review context.
Written standards nest: a root AGENTS.md or CLAUDE.md, and often another in each subproject. Read the chain governing the files this change touches, not only the closest one.
Read each new or changed name against what the code behind it does, and each comment or docstring against the body it describes.
At a public boundary, read the signature and its description as a consumer who cannot see the implementation.
Report an issue when a reader cannot determine the code's intent, constraints, or relationship to established project patterns, or when a surface does not enforce what it claims.
Before suggesting reuse, verify that the existing code is the appropriate precedent.
Do not report a stylistic preference as a defect, though a convention the team has written down is not a preference.
37f0a21
Canonical home
since Aug 8, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.