CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review

Senior engineer code review focused on catching issues before they become PR comments. Reviews only changed lines, categorizes issues by priority, and fixes them one by one. Use when the user says "code review", "review my code", "review this branch", or wants pre-PR feedback.

82

1.29x
Quality

94%

Does it follow best practices?

Impact

84%

1.29x

Average score across 1 eval scenario

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 content is highly actionable and clearly sequenced with strong validation checkpoints and feedback loops. Its main weakness is mild verbosity in the React/TypeScript checklist, which restates some widely-known best practices.

Suggestions

Trim checklist items that restate basic, widely-known practices (e.g. const-vs-let, top-level hooks rules) to keep the skill focused on non-obvious review criteria.

Consider moving the full domain checklist (React/TypeScript/Design System/i18n) into a references/ file and keeping SKILL.md as an overview, improving token efficiency on unrelated tasks.

Add a short note on how to handle very large diffs (e.g. file-count threshold or batching) to make the workflow robust for branch-scale reviews.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands and checklists, but a few checklist items restate widely-known best practices (e.g. basic useState/const-vs-let guidance) that a senior engineer skill could trim.

4 / 5

Actionability

Fully executable guidance throughout: concrete git commands (`git diff main...HEAD`), an exact issue-list format with copy-paste-ready templates, and a step-by-step fix loop with specific prompts.

5 / 5

Workflow Clarity

A clearly numbered Step 0–5 sequence with explicit validation checkpoints (run `just ci`, P0 gating, a two-pass self-check, per-fix approval) and feedback loops that catch errors early.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and a self-contained overview; no bundle files are referenced, which is appropriate, though the long inline checklist could arguably live in a reference file.

4 / 5

Total

18

/

20

Passed

Description

100%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 is strong across all dimensions: concrete actions, natural trigger phrases, explicit what-and-when guidance, and a clear distinct niche. It is concise yet complete.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Reviews only changed lines', 'categorizes issues by priority', and 'fixes them one by one' — with comprehensive, distinct coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what it does (reviews changed lines, categorizes by priority, fixes one by one) and when to use it, with concrete 'Use when...' trigger phrases.

5 / 5

Trigger Term Quality

Provides natural user phrases including 'code review', 'review my code', 'review this branch', and 'pre-PR feedback', covering the common synonyms users would actually say.

5 / 5

Distinctiveness Conflict Risk

The pre-PR, changed-lines-only, priority-categorized niche with explicit natural triggers makes it clearly distinguishable from other review skills with minimal conflict risk.

5 / 5

Total

20

/

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
itsablabla/jada-code
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.