github-pr-workflow

Working with GitHub Pull Requests using the gh CLI. Use for fetching PR details, review comments, CI status, and understanding the difference between PR-level comments vs inline code review comments.

1.06x

Quality

74%

Does it follow best practices?

Impact

85%

1.06x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./github-pr-workflow/SKILL.md

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.

Actionable and token-efficient with copy-paste `gh` commands, a useful bundled script, and the genuinely valuable PR-level-vs-inline-comment distinction. The main weakness is the truncated "Addressing Review Comments" workflow, which lists only two steps and omits the validation/re-verification checkpoint expected for review-driven code changes.

Suggestions

Finish the 'Workflow: Addressing Review Comments' sequence: add steps for re-running `gh-pr-info <PR>` to confirm the thread is resolved/empty, and for replying or marking threads resolved, with an explicit verification checkpoint before considering the review addressed.

Add a validation/feedback loop to the workflow (fix → re-run `gh-pr-info` → confirm no unresolved comments remain → only then proceed/notify), since this is a batch/review operation the rubric expects a validate-then-retry loop for.

Consider moving the 'API Endpoints Reference' block into a separate references/ file and linking to it from the body, which would tighten the SKILL.md overview and lift progressive_disclosure structure.

Dimension	Reasoning	Score
Conciseness	Lean, well-sectioned content with executable commands and tables; assumes Claude's competence and avoids explaining basic git/PR concepts, with only minor table duplication that could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready `gh` commands and API endpoints covering the common cases (view, diff, review, checks, inline comments), plus a concrete bundled script with documented usage and arguments.	5 / 5
Workflow Clarity	The "Workflow: Addressing Review Comments" section is truncated to two steps ("Get unresolved comments" then "Make fixes") with no resolution/verification checkpoint and no feedback loop, leaving the actual multi-step process incomplete.	2 / 5
Progressive Disclosure	Good section structure with a clear overview pointing to the one real bundle script (`gh-pr-info` in scripts/) referenced by name; no separate reference files exist, and content stays one level deep with minor inline API reference that could move to a reference file.	4 / 5
	Total	15 / 20 Passed

Description

78%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 concise, third-person description that clearly scopes the skill to GitHub PR work via the `gh` CLI and surfaces the genuinely non-obvious PR-level vs inline-comment distinction. It explicitly answers both what and when, with only minor keyword/synonym coverage gaps.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("fetching PR details, review comments, CI status") plus the specific concept of distinguishing PR-level vs inline review comments, with only minor gaps in coverage.	4 / 5
Completeness	Answers both "what" (working with GitHub PRs via gh CLI for fetching details/comments/CI) and "when" ("Use for fetching PR details, review comments, CI status..."), with the "when" explicit but slightly list-driven rather than scenario-rich.	4 / 5
Trigger Term Quality	Includes natural phrases a user would say ("PR details", "review comments", "CI status") and the `gh` CLI keyword, but omits common synonyms like "pull request" spelled out and the `.diff`/file-extension style triggers.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to GitHub Pull Requests via the `gh` CLI with the unique distinguishing angle of PR-level vs inline comment types, giving it a clear niche with minimal overlap against generic git skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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: YPares/agent-skills
Path: github-pr-workflow/SKILL.md
Commit: e9d2149

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.