gh-fix-ci
Skill0 starsChanged 30 days agoMITView on GitHub
Debug and fix failing GitHub Actions PR checks using the gh CLI. Use when a GitHub Actions check is failing on a PR and the user wants it diagnosed and fixed.
We split this skill into the rules it gives an agent
15 rules. 5 are common, 0 are distinctive, and 10 are very specific to this project.
5
Common
Most of the 31 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 11
Use gh to locate failing PR checks, fetch GitHub Actions logs for actionable failures, summarize the failure snippet, then propose a fix …
- Very specific: line 12
If a plan-oriented skill (for example create-plan) is available, use it.
- Very specific: line 25
Add --json if you want machine-friendly output for summarization.
- Very specific: line 30
Run gh auth status in the repo.
- Very specific: line 31
If unauthenticated, ask the user to run gh auth login (ensuring repo + workflow scopes) before proceeding.
- Very specific: line 33
Prefer the current branch PR: gh pr view --json number,url.
- Common: line 34
If the user provides a PR number or URL, use that directly.
- Very specific: line 38
Add --json for machine-friendly output.
- Very specific: line 41
If a field is rejected, rerun with the available fields reported by gh.
- Common: line 45
If the run log says it is still in progress, fetch job logs directly:
- Very specific: line 48
If detailsUrl is not a GitHub Actions run, label it as external and only report the URL.
- Common: line 49
Do not attempt Buildkite or other providers.
- Common: line 52
Call out missing logs explicitly.
- Very specific: line 54
Use the create-plan skill to draft a concise plan and request approval.
- Very specific: line 58
After changes, suggest re-running the relevant tests and gh pr checks to confirm.
“Common” is measured: kept by at least 6 in 10 of the 31 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Gh Pr Checks Plan Fix
Overview
Use gh to locate failing PR checks, fetch GitHub Actions logs for actionable failures, summarize the failure snippet, then propose a fix plan and implement after explicit approval.
- If a plan-oriented skill (for example
create-plan) is available, use it; otherwise draft a concise plan inline and request approval before implementing.
Prereq: authenticate with the standard GitHub CLI once (for example, run gh auth login), then confirm with gh auth status (repo + workflow scopes are typically required).
Inputs
repo: path inside the repo (default.)pr: PR number or URL (optional; defaults to current branch PR)ghauthentication for the repo host
Quick start
python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"- Add
--jsonif you want machine-friendly output for summarization.
Workflow
- Verify gh authentication.
- Run
gh auth statusin the repo. - If unauthenticated, ask the user to run
gh auth login(ensuring repo + workflow scopes) before proceeding.
- Run
- Resolve the PR.
- Prefer the current branch PR:
gh pr view --json number,url. - If the user provides a PR number or URL, use that directly.
- Prefer the current branch PR:
- Inspect failing checks (GitHub Actions only).
- Preferred: run the bundled script (handles gh field drift and job-log fallbacks):
python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"- Add
--jsonfor machine-friendly output.
- Manual fallback:
gh pr checks <pr> --json name,state,bucket,link,startedAt,completedAt,workflow- If a field is rejected, rerun with the available fields reported by
gh.
- If a field is rejected, rerun with the available fields reported by
- For each failing check, extract the run id from
detailsUrland run:gh run view <run_id> --json name,workflowName,conclusion,status,url,event,headBranch,headShagh run view <run_id> --log
- If the run log says it is still in progress, fetch job logs directly:
gh api "/repos/<owner>/<repo>/actions/jobs/<job_id>/logs" > "<path>"
- Preferred: run the bundled script (handles gh field drift and job-log fallbacks):
- Scope non-GitHub Actions checks.
- If
detailsUrlis not a GitHub Actions run, label it as external and only report the URL. - Do not attempt Buildkite or other providers; keep the workflow lean.
- If
- Summarize failures for the user.
- Provide the failing check name, run URL (if any), and a concise log snippet.
- Call out missing logs explicitly.
- Create a plan.
- Use the
create-planskill to draft a concise plan and request approval.
- Use the
- Implement after approval.
- Apply the approved plan, summarize diffs/tests, and ask about opening a PR.
- Recheck status.
- After changes, suggest re-running the relevant tests and
gh pr checksto confirm.
- After changes, suggest re-running the relevant tests and
Bundled Resources
scripts/inspect_pr_checks.py
Fetch failing PR checks, pull GitHub Actions logs, and extract a failure snippet. Exits non-zero when failures remain so it can be used in automation.
Usage examples:
python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "123"python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "https://github.com/org/repo/pull/123" --jsonpython "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --max-lines 200 --context 40
Other versions32 projects use a version of this.
Word for word · 0
None found.
Edited · 30
- openai/skills★ 27k89% same
- ComposioHQ/awesome-codex-skills★ 17k70% same
- composio-community/awesome-codex-skills★ 16k70% same
- JetBrains/skills★ 38685% same
- mizchi/skills★ 36986% same
- Nick2bad4u/Uptime-Watcher★ 1587% same
- 4gentic/obelus★ 870% same
- whz39coding/zh-awesome-codex-skills★ 475% same
- hahuyhungdev/ai-coding-config★ 384% same
- daidaibunny/agent-skills★ 289% same
20 more not listed
Wrote their own version · 2
- ulises-jeremias/agent-toolkit★ 19same name
- hebertzhu/agent-foundry★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use codebase-migrate, email-draft-polish and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ComposioHQSkillcodebase-migrate
Run large codebase migrations and multi-file refactors. Uses the Composio CLI to coordinate issue tracking, batched PRs, and CI verification while the agent executes the transforms locally across hundreds of files.
Also in 5 projects that use this
- ComposioHQSkill
email-draft-polish
Draft, rewrite, or condense emails with target tone, length, and audience; use for cold outreach, replies, status updates, or escalations where clarity and brevity matter.
Also in 4 projects that use this
petestewartSkilldatadog-logs
Query Datadog logs via the Logs Search API v2. Use when the user asks to "check the logs", "search logs", "find errors in Datadog", "look up logs for", "show me production logs", "check for errors", "search Datadog", or any request involving log search, error investigation, or production debugging that requires Datadog log data.
Also in 3 projects that use this
MicrosoftSkilldeploy-pipeline
Triggers a Power Platform Pipeline deployment run for a Power Pages solution. Selects a target stage, validates the package, optionally configures deployment settings (environment variables, connection references), then deploys and polls for completion. Use when asked to: "deploy pipeline", "run pipeline", "trigger deployment", "deploy to staging", "deploy to production", "run power platform pipeline", "deploy solution via pipeline", "promote solution", "push to staging", "push to production".
Also in 3 projects that use this
- +8 more from ComposioHQ
In this repository38 other files it gives its agents.
- AGENTS.mdAGENTS.md
- 3d-bloom-sceneSkill
- api-design-reviewSkill
- api-drift-scoutSkill
- api-prompt-optimizerSkill
- autonomy-mapSkill
- behavior-spec-canvasSkill
- cloudflare-deploySkill
- database-designSkill
- docker-debugSkill
- eval-frameworkSkill
- force-graph-3dSkill
- git-workflowsSkill
- glassmorphic-uiSkill
- imagegenSkill
- interactive-artifact-generatorSkill
- pdfSkill
- photo-geolocatorSkill
- playwright-interactiveSkill
- playwrightSkill
- pr-shell-safety-packSkill
- react-query-test-harness-fixerSkill
- repo-first-vercel-buildSkill
- screenshotSkill
- scrutiny-feature-reviewerSkill
- sdk-ui-override-specialistSkill
- security-auditSkill
- security-best-practicesSkill
- security-ownership-mapSkill
- security-threat-modelSkill
- seeded-catalog-syncSkill
- speechSkill
- testing-strategySkill
- transcribeSkill
- user-testing-flow-validatorSkill
- windows-cli-wsl-repairSkill
- windows-node-sandbox-troubleshootingSkill
- workerSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.