CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

github-pr-review

Use when reviewing GitHub pull requests with gh CLI - creates pending reviews with code suggestions, batches comments, and chooses appropriate event types (COMMENT/APPROVE/REQUEST_CHANGES)

Quality

80%

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

Quality

Content

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

Highly actionable content with excellent executable commands, accurate parameter documentation, and a clearly sequenced approval-gated workflow. Its main weakness is verbosity: the same rules are restated many times across padded sections, so a third of the file could be cut without losing guidance.

Suggestions

Cut the 'Red Flags - You're About to Violate the Pattern' and 'Real-World Impact' sections and fold any unique points into 'Core Workflow' — the pending-review and approval mandates are already stated there, removing ~80 lines of repetition.

State each rule once instead of 5-6 times: replace the repeated 'CRITICAL/REQUIRED' emphasis paragraphs in Overview, Prerequisites, Core Workflow, and Red Flags with a single short checklist.

Add brief error-recovery guidance for API failures (e.g., what to do if review creation errors or the commit SHA is stale and the comment line numbers no longer apply) to complete the validation loop.

DimensionReasoningScore

Conciseness

Noticeably verbose with several padded sections: 'Red Flags', 'Real-World Impact', and the 'Why pending reviews?'/'Why approval step?' rationales restate the mandates ('Always use pending reviews', 'CRITICAL: Always get explicit user approval') already given in Overview, Core Workflow, and the Approval Pattern; roughly a third of the ~300 lines is repetition rather than instruction.

2 / 5

Actionability

Fully executable, copy-paste-ready gh api commands with correct -f/-F flag usage, --jq '{id, state}' output checks, a concrete complete example (src/auth.ts line 20, commit 'abc123'), and explicit DO/DON'T syntax rules covering the common cases.

5 / 5

Workflow Clarity

Clear numbered sequence ('Check gh CLI is installed' → 'Draft the review' → 'Show user' → 'Get explicit approval' → 'Post the review') with an explicit validation checkpoint and a 'No, let me revise' feedback loop for the batch posting, so the batch-operation cap does not apply; however, there is no recovery guidance if the gh api call fails or the state is not PENDING.

4 / 5

Progressive Disclosure

A single-file skill (no bundle files exist) with well-organized section headers covering each stage; good structure overall, though the ~300-line length means some inline content (nested-backtick edge case, full installation message, complete example) could be trimmed or split.

4 / 5

Total

15

/

20

Passed

Description

83%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 description: it pairs an explicit 'Use when' trigger with a concrete list of capabilities and named event types, with no vague language. The only weaknesses are minor — a few missing keyword variations and unmentioned capabilities like the approval gate.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'creates pending reviews with code suggestions, batches comments, and chooses appropriate event types (COMMENT/APPROVE/REQUEST_CHANGES)' — but omits other capabilities like the user-approval gate, a minor coverage gap keeping it below the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both questions: 'Use when reviewing GitHub pull requests with gh CLI' gives the trigger, and 'creates pending reviews... batches comments... chooses appropriate event types' gives a concrete what.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('reviewing GitHub pull requests', 'gh CLI', 'code suggestions'), but common variations like 'PR', 'code review', and 'review comments' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (GitHub PR review via gh CLI pending reviews with specific event types) that is mostly distinct, but it could still overlap with generic code-review or PR-commenting skills.

4 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

boarlabsxyz/awesome-mcp

Path

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