CtrlK
BlogDocsLog inGet started
Tessl Logo

github-review-pr

Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for local uncommitted changes — this skill only reviews pull requests on GitHub.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 thorough, highly actionable multi-agent review workflow with an explicitly sequenced process, strong validation gates, and clean one-level-deep reference structure. The only room for improvement is minor redundancy in the posting-guidance prose.

DimensionReasoningScore

Conciseness

The body is dense and operational — most tokens earn their place for a complex 6-agent orchestration — but a few points repeat (the prohibition on posting via `gh pr comment` is stated in step 7 prose, the rules list, and the command-reference comments) and could be trimmed, so it sits at efficient-with-minor-over-explanation rather than fully lean.

4 / 5

Actionability

Provides copy-paste-ready executable guidance throughout — exact `gh` commands, a complete JSON review payload, and exact markdown formats for the review body, inline comments, and blob links covering the common posting cases.

5 / 5

Workflow Clarity

An explicit numbered 8-step sequence (1, 2, 3, 3.5, 4, 5, 6, 7, 8) with validation checkpoints and feedback loops — eligibility re-check at step 6, head-SHA re-fetch, and the confidence≥75 / P0-P1 filter gates — so the destructive/outward-facing posting operation is fully guarded rather than capped at 3.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview that offloads the heavy subagent prompt templates to a single one-level-deep reference (references/subagent-prompts.md), signaled explicitly at three distinct points, with the bundle file present and appropriately split out.

5 / 5

Total

19

/

20

Passed

Description

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

A strong, well-structured description that clearly states the capability, gives comprehensive natural trigger phrases, and adds a negative boundary to reduce conflict risk. Its only weakness is that specificity rests on one elaborated action rather than a list of distinct concrete actions.

DimensionReasoningScore

Specificity

Names the domain and a concrete mechanism ("detailed, multi-perspective code analysis using parallel subagents"), which goes beyond 1-2 generic actions, but it describes one capability elaborated by method rather than a list of distinct concrete actions as in the anchor-5 example.

4 / 5

Completeness

Explicitly answers both what ("Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents") and when ("Use this skill whenever the user wants to review a PR, asks for code review...") with concrete trigger phrases, plus a negative boundary.

5 / 5

Trigger Term Quality

Comprehensive natural terms users would say — "review PR", "check this PR", "look at pull request", plus "PR number" and "GitHub PR URL" synonyms — matching the anchor for full coverage including variations.

5 / 5

Distinctiveness Conflict Risk

Clear niche (GitHub PR review) with an explicit exclusion ("Do NOT use for local uncommitted changes — this skill only reviews pull requests on GitHub") minimizing overlap with local-review skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
feiskyer/claude-code-settings
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.