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 `main`. Adapted from zora-pantheon `.claude/commands/review-pr.md`.

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 ./.agents/skills/review-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

A strongly operational reviewer skill: exact git/gh commands, deterministic helper scripts, severity semantics, and machine-shaped output contracts make it highly actionable with a clear sequenced workflow. It is held back by significant rule repetition across sections, thin failure-path guidance, and a monolithic layout that inlines several checklist/template blocks which belong in reference files.

Suggestions

State the axes-never-merged and inline-comment-only rules once each (§3 and §6) and reference them elsewhere by section number instead of restating them three to four times.

Move the AST01–AST10 checklist, the shell-hazard audit, and the mutation-delta usage guide into a `references/` file (e.g. `references/audits.md`) linked one level deep from the agent briefs, keeping SKILL.md as the orchestration overview.

Add a short failure-path loop for the GitHub step (e.g. what to do when `gh api` fails or no PR number exists) to complement the existing user-confirmation checkpoint.

DimensionReasoningScore

Conciseness

The body is dense and operational (ADR/AST citations, exact commands), but core rules are repeated several times — "their findings are never merged, co-ranked, or interleaved" (§3), restated in §4, §5, and §5b; the inline-comment-only rule appears three times in §6 — and rationale padding like "The goal is: less code to read, less code to maintain. Simpler code is easier to review, test, and debug" explains what Claude already knows. Fits anchor 3 (mostly efficient but could be tightened); not 4 because the repetition and rationale sentences are more than minor.

3 / 5

Actionability

Copy-paste-ready specifics abound: `git merge-base origin/main HEAD`, `scripts/mutation-delta.sh <base-branch>`, `gh api repos/{owner}/{repo}/pulls/{number}/reviews` with `line` and `side: "RIGHT"`, plus exact report/confirm-list templates. Not 5 because the gh api call is described but never given as one complete executable request (no full payload example), and a few agent briefs (e.g. Agent 2 "Verify CRUD symmetry") stay at the direction level.

4 / 5

Workflow Clarity

Steps 0–7 are clearly numbered and sequenced, with real checkpoints: the branch-scope lock runs before any analysis, script output grounds findings, and posting is gated on mandatory user confirmation ("Only after user confirmation, post ALL selected findings"). Not 5 because error-recovery feedback loops are thin — nothing covers gh api failure, a missing PR, or a merge-base that cannot be found; not 3 because the checkpoints that exist are explicit, not implicit.

4 / 5

Progressive Disclosure

The single ~310-line file has clear section headers but no bundle files at all, and self-contained blocks that would suit one-level-deep references are fully inlined: the AST01–AST10 audit checklist, the shell-hazard audit, the ~70-line mutation-delta usage guide, and the report/confirm-list templates. This matches anchor 3 (good structure, but content that should be separate is inline); not 2 because navigation via the numbered sections is easy, not 4+ because nothing is split out.

3 / 5

Total

14

/

20

Passed

Description

71%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 unusually specific about what the skill does — naming all seven sub-agents, both axes, and their outputs — and reads in third person without fluff. Its weakness is the missing 'when to use' half: no explicit trigger guidance, and the terms users most often say for this task (PR, pull request, code review) are absent.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when asked to review a PR, review a branch, or check code before merge.'

Include the natural trigger phrases 'PR', 'pull request', and 'code review' so the skill matches how users actually request it.

Drop or shorten the provenance line 'Adapted from zora-pantheon .claude/commands/review-pr.md' — it spends description budget on non-capability information.

DimensionReasoningScore

Specificity

"runs 6 specialized parallel sub-agents (Security, API/CRUD, Pattern enforcement, Simplicity, Reuse/DRY, Test hygiene) producing a severity-based report" and "runs a 7th fresh-context sub-agent producing a behavior-change confirm-list" — multiple named concrete actions with their outputs, comprehensive coverage of what the skill does. Not 4 because coverage of capabilities is essentially complete rather than having minor gaps.

5 / 5

Completeness

The 'what' is explicit and detailed (two axes, sub-agents, severity report, confirm-list), but there is no 'Use when...' clause or equivalent trigger guidance — "Scoped to the current branch's diff against `main`" states scope, not when to invoke. Per the rubric guideline, a missing explicit trigger caps completeness at 3; it is not 2 because the 'what' is clear and specific.

3 / 5

Trigger Term Quality

Natural terms present include "senior reviewer", "diff", "branch", "security", "test hygiene", which map to how users ask for reviews; however the most common phrasings for this task — "PR", "pull request", "code review" — never appear. Fits anchor 4 (good coverage, a few natural terms missing) rather than 5, which demands synonyms/extensions coverage.

4 / 5

Distinctiveness Conflict Risk

"Two-axis senior reviewer", "Axes are never merged", and the fresh-context behavior confirm-list describe a distinctive methodology that separates it from generic review skills. Not 5 because it still competes with any general code-review/PR-review skill on overlapping trigger words (review, diff, branch).

4 / 5

Total

16

/

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: 3 possibly missing (scripts/behavior-delta.sh, scripts/guards.config.sh, scripts/mutation-delta.sh)

Warning

Total

15

/

16

Passed

Repository

agranado2k/ai-report-platform

Path

.agents/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.