code-review-checklist

Comprehensive checklist for conducting thorough code reviews covering functionality, security, performance, and maintainability

Install with Tessl CLI

npx tessl i github:sickn33/antigravity-awesome-skills --skill code-review-checklist

What are skills?

0.98x

Quality

37%

Does it follow best practices?

Impact

97%

0.98x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/code-review-checklist/SKILL.md

SKILL.md

Review

Evals

Discovery

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies its purpose as a code review checklist and mentions key review areas, but lacks concrete actions and explicit trigger guidance. Without a 'Use when...' clause, Claude cannot reliably determine when to select this skill over others. The description reads more like a title than actionable selection criteria.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'review my code', 'PR review', 'pull request feedback', 'code quality check'

Replace abstract categories with specific actions: 'Checks for SQL injection, validates input sanitization, identifies N+1 queries, flags missing error handling'

Include file type triggers like '.py', '.js', 'diff', 'patch' to help distinguish from general coding assistance

Dimension	Reasoning	Score
Specificity	Names the domain (code reviews) and lists categories of concerns (functionality, security, performance, maintainability), but doesn't describe concrete actions like 'identify vulnerabilities', 'check for race conditions', or 'verify test coverage'.	2 / 3
Completeness	Describes what (checklist for code reviews) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes 'code reviews' which users would naturally say, but misses common variations like 'PR review', 'pull request', 'review my code', 'code feedback', or 'review checklist'.	2 / 3
Distinctiveness Conflict Risk	Somewhat specific to code reviews, but could overlap with general coding assistance skills or security audit skills. The broad categories (security, performance) could trigger conflicts with more specialized skills.	2 / 3
	Total	7 / 12 Passed

Implementation

42%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides comprehensive, actionable checklists with good code examples, but suffers from severe verbosity and poor organization. It explains obvious concepts Claude already knows and presents everything in a single massive file rather than using progressive disclosure. The workflow lacks validation checkpoints for handling review findings.

Suggestions

Remove the 'Overview', 'When to Use This Skill', and 'How It Works' sections - Claude knows what code review is and when to use a checklist

Split into multiple files: keep SKILL.md as a quick reference with the 'Complete Review Checklist', move detailed examples to EXAMPLES.md, templates to TEMPLATES.md, and pitfalls to PITFALLS.md

Add a workflow for handling findings: prioritization criteria, when to block vs. request changes vs. approve with comments, and how to track resolution

Reduce the three detailed example checklists to one concise example, referencing a separate file for additional domain-specific checklists

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanations of concepts Claude already knows (what code review is, why it matters). The 'When to Use This Skill' and 'How It Works' sections explain obvious concepts. The document is over 400 lines when the core checklists could be presented in under 100.	1 / 3
Actionability	Provides concrete, executable checklists with specific items to check. Code examples are complete and show clear good/bad patterns. The checklist items are specific and actionable (e.g., 'No SQL injection vulnerabilities' with parameterized query examples).	3 / 3
Workflow Clarity	Steps are listed (Step 1-6) but lack validation checkpoints or feedback loops. There's no guidance on what to do when issues are found, how to prioritize findings, or when to block vs. approve. The 'Pre-Review' checklist mentions running locally but doesn't integrate with the main workflow.	2 / 3
Progressive Disclosure	Monolithic wall of text with everything inline. The 'Related Skills' and 'Additional Resources' sections reference external content but the main body dumps all checklists, examples, templates, and pitfalls into one massive file. Content like 'Review Comment Templates' and 'Common Pitfalls' should be separate files.	1 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Reviewed: about 18 hours ago

Table of Contents

Discovery Implementation Validation

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.