euxx/gh-fix-ci
skills/gh-fix-ci/SKILL.md
Debug failing GitHub Actions CI checks on the current branch's PR using the gh CLI — inspect logs, summarize root cause, and propose a focused fix plan before implementing.
tools
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add euxx/claude-skills-for-copilot gh-fix-ciInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 2:38 PM4.6s1 file scanned
SKILL.md
- name:
- gh-fix-ci
- description:
- Debug failing GitHub Actions CI checks on the current branch's PR using the gh CLI — inspect logs, summarize root cause, and propose a focused fix plan before implementing.
- argument-hint:
- [PR number or URL (optional; defaults to current branch PR)]
- user-invocable:
- true
Fix Failing CI Checks
Use gh to locate failing PR checks, fetch GitHub Actions logs, summarize the failure, then propose a fix plan and implement only after explicit user approval.
Prerequisites
Verify gh authentication before doing anything else:
gh auth status
If unauthenticated, ask the user to run gh auth login (repo + workflow scopes required), then stop.
Workflow
1. Resolve the PR
# if the user specified a PR number or URL:
gh pr view <number-or-url> --json number,url,headRefName
# otherwise (current branch):
gh pr view --json number,url,headRefName
Extract owner and repo from the returned url field — PR URLs have the form https://github.com/<owner>/<repo>/pull/<number>, so split on / to get the 4th and 5th segments. These are the base (target) repository coordinates where GitHub Actions checks run, and are reliable even for cross-fork PRs.
2. Inspect failing checks
gh pr checks <pr-number> -R <owner>/<repo> --json name,state,bucket,link,startedAt,completedAt,workflow
If a field is rejected, rerun with the available fields reported by gh. Scope only to GitHub Actions checks. If link is not a GitHub Actions run URL, label it as external, report the URL only, and do not investigate further (e.g. Buildkite, CircleCI are out of scope).
3. Fetch failure logs
For each failing GitHub Actions check:
- Extract the run ID from
link(the numeric segment in the URL). - Fetch run metadata:
gh run view <run-id> -R <owner>/<repo> --json name,workflowName,conclusion,status,url,event,headBranch,headSha - Fetch logs:
gh run view <run-id> -R <owner>/<repo> --log - If the run is still in progress, get the job IDs and fetch logs directly:
Then for each relevant job:gh run view <run-id> -R <owner>/<repo> --json jobsgh api "/repos/<owner>/<repo>/actions/jobs/<job-id>/logs"
Extract a concise failure snippet (relevant error lines and stack traces only).
4. Summarize failures
Present a short summary for the user:
- Check name and run URL
- Root cause (1–2 sentences with supporting log snippet)
- Note if logs are missing or truncated
5. Plan and get approval
Draft a concise fix plan covering:
- Which files to change and why
- Any tests that need updating
- Expected outcome
Ask the user for explicit approval before implementing.
6. Implement
Apply the approved plan. Show a summary of diffs and note any tests run.
7. Recheck
After changes, suggest:
gh pr checks <pr-number> -R <owner>/<repo> --watch
to confirm the checks pass.
Related Skills
euxx/type-design-analyzer
testing
VerifiedTrustedCommunity
Analyzes type design quality by rating encapsulation, invariant expression, usefulness, and enforcement. Helps design types that make invalid states unrepresentable. Use when reviewing new types or data models.
SKILL.mdUpdated Apr 16, 2026
euxx/test-analyzer
testing
VerifiedTrustedCommunity
Reviews test coverage quality from a behavioral perspective, identifying critical gaps and test quality issues. Does not check line coverage — checks meaningful scenario coverage. Use after adding or modifying tests.
SKILL.mdUpdated Apr 16, 2026
euxx/silent-failure-hunter
development
VerifiedTrustedCommunity
Audits error handling for silent failures, inadequate user feedback, and unjustified fallback behavior. Finds issues in catch blocks, fallbacks, and error paths. Use after modifying error handling code.
SKILL.mdUpdated Apr 16, 2026
euxx/security-threat-model
development
VerifiedTrustedCommunity
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.
SKILL.mdUpdated Apr 16, 2026