CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-review

Perform a pedantic, multi-perspective code review on the current diff or git changes against the styleguide and software engineering best practices.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/code-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

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 protocol with clear sequencing and a thoughtful subagent handoff. Its main weakness is token efficiency: the shell-scripting efficiency pass and a few examples teach concepts Claude already knows, and there is no output example to anchor the expected format. Moving the detailed shell idioms to a reference file would improve both conciseness and progressive disclosure.

Suggestions

Trim or move the shell-scripting efficiency details (parameter expansion vs basename/dirname, grep -F guidance) to a reference file, trusting Claude's existing knowledge of shell builtins.

Add a short example of the expected output format showing the severity tags ([MUST-FIX], [CONCERN], [NIT]) in context.

Remove explanations of known concepts such as the O(N^2) parenthetical and the non-negative-integer regex example.

DimensionReasoningScore

Conciseness

The checklist is mostly efficient, but several passages explain concepts Claude already knows, e.g. 'Prefer Bash parameter expansion (e.g., ${var##*/} instead of basename...)', 'quadratic complexity ($O(N^2)$) algorithms', and the regex example '^[0-9]+$ for non-negative integers in bash'. Not 4: these are more than minor instances of over-explanation; not 2: the majority of the body is lean, actionable instruction.

3 / 5

Actionability

Concrete, executable guidance throughout: exact styleguide path '.gemini/styleguide.md', defined severity tags, specific shell idioms, and 'Retrieve the current changes (using git diff)'. Not 5: there is no copy-paste example of the expected review output format; not 3: the guidance is directly executable rather than pseudocode.

4 / 5

Workflow Clarity

Steps are clearly sequenced (pre-flight check, context gathering, analysis, output) with a conditional branch and an explicit failure path ('use the send_message tool to notify me immediately'). Not 5: there is no explicit validation checkpoint on the review output itself; not 3: checkpoints like the pre-flight check and subagent handoff are present and explicit.

4 / 5

Progressive Disclosure

No bundle files exist, so this is scored on the body alone: sections are well-organized (## Review Protocol, ### Pass 1-3, ## Step-by-Step Execution) and the single external reference (.gemini/styleguide.md) is clearly signaled. Not 5: at ~58 lines with the detailed shell-efficiency sub-list inlined, some content would fit better in a separate reference file.

4 / 5

Total

15

/

20

Passed

Description

57%Weight 40%Scale 1-5

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 communicates a clear single purpose but reads as a role statement rather than a trigger-optimized description. It lacks an explicit 'Use when...' clause and does not enumerate the concrete review capabilities found in the body. Adding trigger phrases and specific capabilities would raise most dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to review code, the diff, or git changes before committing or pushing.'

Enumerate the concrete capabilities from the body (logic defects, security vulnerabilities, resource leaks, styleguide violations) instead of the vague 'software engineering best practices'.

Include natural synonyms such as 'pull request' or 'review my changes' to broaden trigger coverage and distinguish from general review skills.

DimensionReasoningScore

Specificity

Names the domain ('code review') and 1-2 concrete actions ('on the current diff or git changes', 'against the styleguide'), but never enumerates what the review actually covers (bugs, security, leaks, style). Not 4: it does not list several specific actions; not 2: the actions named are concrete rather than generic.

3 / 5

Completeness

The 'what' is clear ('pedantic, multi-perspective code review on the current diff'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4: the 'when' is not even weakly stated.

3 / 5

Trigger Term Quality

'code review', 'diff', and 'git changes' are phrases users naturally say, giving good keyword coverage. Not 5: common variations like 'pull request', 'PR', or 'review my changes' are missing.

4 / 5

Distinctiveness Conflict Risk

'Against the styleguide' and 'diff or git changes' add specificity, but the generic 'code review' framing could overlap with PR-review, lint, or general review skills. Not 4: no distinctive trigger sets it clearly apart from closely related review skills.

3 / 5

Total

13

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

flutter/flutter-intellij

Path

.agents/skills/code-review/SKILL.md

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.