A suite of focused code-review skills for Tessl Agent and GitHub Actions review workflows (`tessl change review`). Each review lens is its own skill, so a workflow can invoke one lens or several. Fork and tune any skill for your own repository.
—
—
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
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.