github-pr-workflow
tessl i github:YPares/agent-skills --skill github-pr-workflowWorking 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.
Validation
81%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
Implementation
88%This is a well-crafted skill that efficiently communicates the critical distinction between PR-level and inline comments - knowledge that prevents common mistakes. The content is actionable with executable commands and a useful script reference. The main weakness is the truncated workflow section which leaves the review-fix cycle incomplete.
Suggestions
Complete the 'Workflow: Addressing Review Comments' section with steps 3+ (commit, push, verify comments addressed)
Add a validation step to the workflow (e.g., re-run gh-pr-info to confirm comments resolved)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, assuming Claude's competence with GitHub and CLI tools. No unnecessary explanations of what PRs are or how GitHub works - jumps straight to the key distinction between comment types and actionable commands. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands throughout. The command reference table, bash examples, and API endpoints are all immediately executable with clear parameter placeholders. | 3 / 3 |
Workflow Clarity | The 'Workflow: Addressing Review Comments' section is incomplete - it starts with steps 1 and 2 but appears truncated. While the script table and commands are clear, the workflow lacks completion and validation checkpoints for the review-fix-push cycle. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from concepts to scripts to commands to API reference. The script reference table provides a clean overview, and API endpoints are appropriately separated for when deeper access is needed. | 3 / 3 |
Total | 11 / 12 Passed |
Activation
N/ASomething went wrong
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.