Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-structured, actionable guide with executable gh CLI commands and a clear five-step workflow that respects Claude's intelligence. It is solidly above the midpoint on all dimensions, with only minor tightening and consolidation opportunities.
Suggestions
Tighten the 'Common CI Check Names' and 'Example Commands' sections or fold them into the workflow steps to reduce token overhead and lift conciseness toward 5.
Add one explicit feedback loop for log extraction (e.g., if `--log-failed` returns truncated output, retry with `gh run view --log` or download the full log archive) to push workflow clarity higher.
Show a brief jq/grep snippet for parsing `statusCheckRollup` into failed-check names and run IDs, closing the main actionability gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient, using code blocks for commands and assuming Claude's competence rather than explaining CI/gh concepts; minor padding appears in the 'Common CI Check Names' list and some 'Important Notes' that restate earlier points, placing it above the 3-anchor but not fully lean. | 4 / 5 |
Actionability | Provides mostly executable guidance — concrete `GH_PAGER=cat gh pr view ... --json statusCheckRollup` and `gh run view <run-id> --log-failed` commands with appropriate placeholders and a copy-paste-ready 'Example Commands' section — with minor gaps such as how to parse the statusCheckRollup JSON. | 4 / 5 |
Workflow Clarity | A clear five-step sequence (verify PR → check status → extract logs → categorize → generate plan) with explicit handling of in-progress CI and validation steps embedded in the plan output; the skill is deliberately non-destructive (plan-only), so the destructive-cap does not apply, but explicit error-recovery feedback loops are only implied rather than spelled out. | 4 / 5 |
Progressive Disclosure | Well-organized into clearly labeled sections (Overview, Workflow, Important Notes, Common CI Check Names, Example Commands) with appropriately signaled cross-references to the `create-pr` and `fix-errors` skills; no bundle files exist or are needed, but it sits just below the top anchor because a couple of sections (Common CI Check Names, Example Commands) could be consolidated. | 4 / 5 |
Total | 16 / 20 Passed |