fix-ci-failures

Investigate and fix CI failures on a pull request. Use when CI checks fail on a PR branch — covers finding the PR, identifying failed checks, downloading logs and artifacts, extracting the failure cause, and iterating on a fix. Requires the `gh` CLI.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

A highly actionable, well-sequenced CI debugging runbook with concrete commands and solid validation/feedback loops. The only gap is that everything lives inline in SKILL.md rather than splitting detailed reference material into bundle files.

Suggestions

Move the detailed 'VS Code Log Artifacts Structure' and 'Recognizing Infrastructure / Flaky Failures' catalogs into a references/ file (e.g. reference.md) and link to it from the body to improve progressive disclosure.

Trim the advisory Tip/Warning/Why callouts to one line each or fold them into the preceding command comments to tighten conciseness.

Add a brief local-reproduction validation step in Step 7 that runs the exact failing test before pushing, making the feedback loop fully explicit.

Dimension	Reasoning	Score
Conciseness	Mostly lean and command-driven with operational explanations Claude would not already know, but a few Tip/Warning/Why notes could be trimmed without losing clarity.	4 / 5
Actionability	Fully executable, copy-paste-ready gh/git/grep commands with specific jq filters and example artifact names covering the common failure cases.	5 / 5
Workflow Clarity	Clear 7-step sequence with an explicit validation checkpoint (Step 6: is the failure PR-related or infra?) and feedback loops (Step 7: typecheck, run local tests, watch CI; re-run failed jobs and check main on persistent failures).	5 / 5
Progressive Disclosure	Well-organized into numbered steps plus a Quick Reference navigation table, but it is a single-file inline runbook with no one-level-deep references to split out the detailed artifact/infra catalogs.	4 / 5
	Total	18 / 20 Passed

Description

92%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, concrete description that clearly states both purpose and trigger conditions with multiple specific actions. Only minor keyword-synonym coverage keeps it from a perfect score on trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'finding the PR, identifying failed checks, downloading logs and artifacts, extracting the failure cause, and iterating on a fix' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' ('Investigate and fix CI failures on a pull request') and 'when' ('Use when CI checks fail on a PR branch') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural triggers like 'CI failures' and 'CI checks fail on a PR branch' that users would actually say, though a few common variations (e.g. 'broken build', 'red CI', 'failing tests') are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (PR CI failures via the gh CLI) with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	19 / 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: posit-dev/positron
Path: .github/skills/fix-ci-failures/SKILL.md
Commit: 75a1182

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.