CtrlK
BlogDocsLog inGet started
Tessl Logo

code-reviewer

Review pull requests, diffs, and code changes across behavior, contracts, tests, maintainability, and documentation. Use when the user asks for review of a PR, patch, diff, commit, or code change.

80

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a well-structured, actionable review playbook that stays lean while assuming Claude's competence and offloading scope detail to verified reference files. Workflows are clearly sequenced with finding-verification checkpoints and a concrete output template.

DimensionReasoningScore

Conciseness

The body is dense, directive, and high-signal with no padding or explanation of concepts Claude already knows; every section (scopes table, command cues, template) earns its place. It is long but lean rather than verbose.

3 / 3

Actionability

Provides concrete executable commands (gh pr view/diff, git diff with merge-base), a copy-paste delegate prompt template, explicit severity/confidence definitions, and a full output template with expected fields.

3 / 3

Workflow Clarity

Clear sequence from Review Setup through Safety, Flow, Findings Bar, Severity, and Output, with verification of findings against the diff and nearby code; the read-mostly nature means the destructive-feedback-loop cap does not apply.

3 / 3

Progressive Disclosure

SKILL.md serves as a concise overview with five clearly signaled one-level-deep references (references/behavior.md, contract.md, test.md, simplicity.md, documentation.md), all verified to exist as real files, with content appropriately split.

3 / 3

Total

12

/

12

Passed

Description

100%

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 is specific, trigger-rich, and complete with explicit what-and-when guidance in third person. It is concise yet covers the review domain and its natural invocation terms well.

DimensionReasoningScore

Specificity

Names the domain plus multiple concrete review actions across six explicit scopes ('behavior, contracts, tests, maintainability, and documentation'), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('Review pull requests, diffs, and code changes...') and when via a clear 'Use when the user asks for review of a PR, patch, diff, commit, or code change' trigger clause.

3 / 3

Trigger Term Quality

Includes natural terms users actually say ('PR, patch, diff, commit, or code change') with good variation coverage, matching the 'good coverage of natural terms' anchor.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (reviewing diffs/PRs) with distinct triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
shillem/cc-marketplace
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.