CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-pr

Review Apache ShardingSphere or user-authorized downstream pull requests and PR discussions from public or authorized repository evidence. Use for code-correctness or mergeability decisions, CI-focused review, root-cause and regression analysis, complete consolidated findings, copy-ready committer feedback, challenged findings, multi-round review, and formal review of local implementation candidates in the repository completion loop.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 provides a rigorous, well-sequenced multi-gate review workflow with concrete commands, exact output contracts, and explicit validation loops — excellent workflow clarity and good actionability. Its weaknesses are token efficiency (repeated restatement of the same rules across sections and dense prose) and progressive disclosure (heavy ledger/JSON documentation inlined in SKILL.md instead of a reference file, plus unverifiable out-of-bundle links).

Suggestions

Move the ledger operation details, JSON shape examples, and batching rules from "Completion Gate and Scripts" into a dedicated reference file (e.g., references/ledger-usage.md), keeping only the script names, trigger conditions, and validation requirements in SKILL.md.

State each Checkstyle/Spotless and CI-exclusion rule once in its owning section (Mandatory Style Verification Gate / Review Focus) and reference it from the Review Workflow, Completion Gate, and Formal Decision Contract instead of restating it in each place.

Add a worked JSON example for the `--applicability` actual-value-naming input (with `variable`, `operation`, `role`, `declaration`, `operation_call`, `use`), and either verify or provide fallbacks for the out-of-bundle links (../code-implementation/..., ../../../context/change-completion.md) so the skill remains navigable when those siblings are absent.

DimensionReasoningScore

Conciseness

Nearly all content is project-specific review policy Claude would not already know, but there is noticeable repetition (Checkstyle/Spotless and CI-exclusion rules are restated across "Review Focus", "Mandatory Style Verification Gate", "Review Workflow", "Completion Gate", and "Formal Decision Contract") and long convoluted sentences (e.g., "Preserve later user approvals with their actual provenance instead of treating approval of an implementation choice as proof of an original version requirement or of its necessity") that could be tightened. This sits between anchor 2's padded verbosity and anchor 4's efficient-but-trimmable text.

3 / 5

Actionability

Guidance is mostly executable: concrete script invocations ("scripts/manage_review_ledger.py validate-incomplete --ledger <ledger>", "scripts/build_review_inventory.py --format json", the batch operations syntax), exact output contracts ("### Result" with "exactly one `Review Result: Mergeable` line"), P0/P1/P2 definitions, and JSON shape examples. Minor gaps remain — e.g., the `--applicability` JSON fields for actual-value-naming findings are enumerated in prose ("`variable`, `operation`, `role`, `declaration`, `operation_call`, and `use`") without a worked example, keeping it below anchor 5.

4 / 5

Workflow Clarity

The Review Workflow is a numbered 9-step sequence with explicit validation checkpoints (Problem and Project Commitment Gate, Finding Proof Gate, Mandatory Style Verification Gate, ledger validation "before selecting the result") and a convergence feedback loop ("If it finds a new independent candidate, return to step 6"), plus a fully specified decision mapping in the Formal Decision Contract. This matches anchor 5's clear sequence, explicit validation, and error-recovery loops.

5 / 5

Progressive Disclosure

The five local references (evidence-access, high-risk-review, sql-parser-review, review-coordination, review-corrections) are real files, clearly signaled with read conditions ("Read only the triggered sections of...", "through EOF"), and only one level deep — good practice. However, the 355-line body inlines extensive ledger-operation documentation, JSON shapes, and batching rules in "Completion Gate and Scripts" that clearly belong in a separate reference file (anchor 3: "content that should be separate is inline"), and several links (../code-implementation/..., ../../../context/change-completion.md) resolve outside the bundle and cannot be verified from it.

3 / 5

Total

15

/

20

Passed

Description

92%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: third-person voice, a precise domain scoping to Apache ShardingSphere (and authorized downstreams), a comprehensive list of concrete review capabilities, and an explicit "Use for..." trigger clause. The only weakness is that a few natural user phrasings like "code review" or "can this be merged" are not literally present.

DimensionReasoningScore

Specificity

The description lists multiple concrete review actions — "code-correctness or mergeability decisions, CI-focused review, root-cause and regression analysis, complete consolidated findings, copy-ready committer feedback, challenged findings, multi-round review" — giving comprehensive coverage of the skill's capabilities. It exceeds anchor 4 because the action list covers essentially every review mode the skill supports rather than leaving minor gaps.

5 / 5

Completeness

It explicitly answers both questions: the "what" is "Review Apache ShardingSphere or user-authorized downstream pull requests and PR discussions from public or authorized repository evidence", and the "when" is an explicit "Use for..." clause enumerating concrete trigger scenarios. This matches anchor 5's requirement of a clear what plus explicit when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger terms are present — "pull requests", "PR discussions", "mergeability", "CI-focused review", "regression analysis", "committer feedback", "multi-round review" — including the pull requests/PR synonym pair. A few natural user phrasings (e.g., "code review", "can this be merged/approved") are not literally covered, which keeps it below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Apache ShardingSphere or user-authorized downstream pull requests" carves out a clear niche with distinct triggers (committer feedback, repository completion loop), giving minimal overlap risk with generic code-review skills. It is clearly more distinct than anchor 4's "minor overlap risk with closely related skills".

5 / 5

Total

19

/

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

relative_links

Relative link issues: 6 suspicious

Warning

Total

15

/

16

Passed

Repository

apache/shardingsphere

Path

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