CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-code-review

Review GitHub pull requests using gh CLI and the GitHub API. Use when asked to review a PR, inspect PR changes, or choose approve/comment/request-changes.

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured, highly actionable skill for PR review with clear workflow sequencing, explicit constraints, and concrete commands. Its main weakness is moderate verbosity from repeated prohibitions across multiple sections and a monolithic structure that could benefit from splitting reference material into separate files. The defensive guardrails (error handling, call budget, hard rules) are thorough and appropriate for an operation involving external API calls.

Suggestions

Consolidate the repeated prohibitions (e.g., 'do not manually call the PR Files API') into a single constraints section rather than restating them in hard rules, workflow steps, and call budget.

Consider extracting the detailed output format specification and review focus checklist into separate referenced files to reduce the main SKILL.md length.

DimensionReasoningScore

Conciseness

The skill is mostly efficient and avoids explaining concepts Claude already knows, but it's quite lengthy with repetitive prohibitions (e.g., 'do not manually call the PR Files API' appears in multiple forms across several sections). The call budget section partially duplicates constraints already stated in hard rules and workflow steps.

2 / 3

Actionability

Provides fully concrete, executable commands with exact script paths, environment variable patterns, and specific invocation examples. The output format is precisely specified with tags, character limits, and section structure. The error block template is copy-paste ready.

3 / 3

Workflow Clarity

The workflow is clearly sequenced (identify PR → collect data → targeted patches → raw files → optional checks → review output) with explicit validation checkpoints (PATCHES_SKIPPED triggers step 3, 404 handling, authentication failure handling) and a well-defined error recovery path. The call budget section acts as an explicit constraint checklist.

3 / 3

Progressive Disclosure

The skill references external scripts (collect_pr.sh, fetch_targeted_patches.sh, fetch_raw_files.sh) which is good progressive disclosure, but no bundle files were provided to verify their existence. The SKILL.md itself is a long monolithic document that could benefit from splitting the output format specification or review focus checklist into separate reference files.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong, well-crafted description that clearly communicates the skill's purpose, tools, and trigger conditions. It uses third person voice, lists concrete actions, includes natural trigger terms, and has an explicit 'Use when' clause with specific scenarios. The description is concise yet comprehensive enough to distinguish it from related skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'Review GitHub pull requests', 'inspect PR changes', 'approve/comment/request-changes'. Also specifies the tools used: 'gh CLI and the GitHub API'.

3 / 3

Completeness

Clearly answers both 'what' (review GitHub pull requests using gh CLI and GitHub API) and 'when' (explicit 'Use when asked to review a PR, inspect PR changes, or choose approve/comment/request-changes').

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'review a PR', 'PR changes', 'approve', 'comment', 'request-changes', 'pull requests', 'GitHub'. These cover common variations of how users would phrase PR review requests.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — focuses specifically on PR review workflows with explicit actions (approve/comment/request-changes) and specific tooling (gh CLI, GitHub API). Unlikely to conflict with general GitHub or code review skills.

3 / 3

Total

12

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
bkircher/skills
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.