code-review-checklist
Code review guidelines covering code quality, security, and best practices.
Install with Tessl CLI
npx tessl i github:lchenrique/politron-ide --skill code-review-checklist83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable code review checklist that efficiently covers key areas including modern AI-specific concerns. The concrete code examples and emoji-based comment conventions are particularly strong. The main weakness is the lack of explicit workflow guidance for how to conduct the review process itself and when to escalate or block.
Suggestions
Add a brief workflow section at the top explaining the recommended order of review (e.g., 'Start with security, then correctness, then quality') with guidance on when to stop and request changes vs continue reviewing
Consider splitting AI/LLM patterns and anti-patterns into separate reference files with links, keeping SKILL.md as a quick-reference overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using checklists and code examples without explaining concepts Claude already knows. No unnecessary padding or verbose explanations of basic programming concepts. | 3 / 3 |
Actionability | Provides concrete, executable guidance with specific code examples showing anti-patterns vs correct patterns, clear emoji-based comment conventions, and copy-paste ready TypeScript examples. | 3 / 3 |
Workflow Clarity | The checklist format provides clear categories but lacks explicit sequencing for the review process itself. No validation checkpoints or feedback loops for how to proceed when issues are found during review. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but everything is inline in one file. For a comprehensive code review guide, some sections (like AI/LLM patterns or anti-patterns) could be split into separate reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
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.