CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-pr

Two-axis senior reviewer. Axis 1 (standards, "is it built right?") runs 6 specialized parallel sub-agents (Security, API/CRUD, Pattern enforcement, Simplicity, Reuse/DRY, Test hygiene) producing a severity-based report. Axis 2 (spec & behavior, "is it the right thing?") runs a 7th fresh-context sub-agent producing a behavior-change confirm-list for the human. Axes are never merged. Scoped to the current branch's diff against the default branch.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/review-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 an exceptionally actionable, well-sequenced orchestration protocol with exact commands, templates, and user-confirmation gates — top marks on actionability and workflow clarity. Its weaknesses are token efficiency (the axis-separation and mutation rules are repeated many times) and progressive disclosure (a monolithic 300-line file with no reference files despite containing several self-contained checklists and output contracts).

Suggestions

State the two-axes-never-merged rule once in the §3 preamble and reference it by number elsewhere instead of restating it in §5, §5b, and §6 — this alone would trim significant tokens.

Move the self-contained blocks (AST01–AST10 agentic-skill audit checklist, mutation-delta usage protocol, §5/§5b output format contracts) into reference files under references/ and link to them one level deep, keeping SKILL.md as the orchestration overview.

Cut justificatory prose ('This ensures the review is focused...', 'Merging them destroys both') — the operational rules are self-explanatory to a competent reader.

DimensionReasoningScore

Conciseness

Mostly efficient operational directives, but with several padded/repeated passages: the 'axes are never merged' rule is restated roughly six times ('Merging them destroys both', §3 preamble, §5, §5b, §6), the mutation-delta protocol is fully specified twice (Agents 6 and 7), and justifications like 'This ensures the review is focused, actionable...' explain reasoning Claude does not need. The repetition goes beyond the 'minor instances' of 4 but the bulk is purposeful instruction rather than the pervasive padding of 2.

3 / 5

Actionability

Fully executable throughout: exact git commands ('git merge-base origin/<default-branch> HEAD', 'git diff <merge-base>..HEAD --name-only'), the exact posting API ('gh api repos/{owner}/{repo}/pulls/{number}/reviews'), verbatim output templates, per-agent checklists with citation formats, and the exact closing question to ask. Copy-paste ready with specific contracts covering the common cases.

5 / 5

Workflow Clarity

Steps 0–7 are explicitly sequenced with mandatory checkpoints, and the one destructive/batch operation (posting PR comments) is gated by validation: 'Only after user confirmation, post ALL selected findings as inline review comments in a single API call', with feedback handling ('Edit that same comment if the diff changes') and a hard stop ('This skill never merges'). Clear sequence, explicit validation, feedback loops, and checklists.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent) and everything is inlined in one ~300-line file. Internal structure is good (numbered protocol steps, per-agent headers), but blocks that clearly belong in separate reference files — the AST01–AST10 audit checklist, the mutation-delta protocol, the §5/§5b output contracts — are inline with zero external references, matching 'content that should be separate is inline' rather than the minimal-structure wall of 2.

3 / 5

Total

16

/

20

Passed

Description

58%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 specific and structurally distinctive about what the skill does, but it omits any 'when to use' trigger guidance and misses the most natural invocation phrases ('code review', 'PR', 'pull request'). It reads as an architecture summary rather than a trigger-facing description.

Suggestions

Add an explicit trigger clause, e.g. 'Use when asked to review a PR, do a code review, or review the current branch's changes before merge.'

Include the natural trigger terms users actually say — 'code review', 'PR', 'pull request', 'review my branch' — so the skill is discoverable for its primary use case.

State the PR-comment posting outcome (it is a major part of the skill's behavior) so the 'what' coverage is comprehensive.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'runs 6 specialized parallel sub-agents (Security, API/CRUD, Pattern enforcement, Simplicity, Reuse/DRY, Test hygiene)', 'producing a severity-based report', 'behavior-change confirm-list' — with named lenses. Falls short of 5 because coverage has gaps: the PR-comment posting flow is absent and the word 'code' never appears, leaving 'reviewer of what' implied.

4 / 5

Completeness

The 'what' is clear (two-axis review, 7 sub-agents, severity report + confirm-list), but there is no 'Use when...' clause or equivalent explicit trigger guidance; 'Scoped to the current branch's diff' states scope, not invocation conditions. Per the rubric guideline, a missing 'when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Some relevant natural keywords ('reviewer', "branch's diff", 'Security', 'API') but the phrases a user would most naturally say — 'code review', 'PR', 'pull request' — are missing, and the skill's main delivery vehicle (PR comments) is untriggerable from the description. Better than 2 (more than one or two generic keywords) but not the 'good coverage, a few missing' of 4 since the primary triggers are the ones absent.

3 / 5

Distinctiveness Conflict Risk

The two-axis framing and named lenses ('Reuse/DRY', 'Test hygiene', 'confirm-list') carve a mostly distinct niche with minimal conflict risk against unrelated skills. Not 5 because 'reviewer' is broad and other code-review skills would overlap on the same triggers since 'code review'/'PR' are never claimed explicitly.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 possibly missing (scripts/behavior-delta.sh, scripts/guards.config.sh)

Warning

Total

15

/

16

Passed

Repository

agranado2k/tic-tac-toe-with-agentic-sdlc

Path

.claude/skills/review-pr/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.