bahayonghang/gh-fix-ci
skills/git-github-collaboration/gh-fix-ci/SKILL.md
Debug and fix failing GitHub PR checks with GitHub CLI. Use when GitHub Actions checks fail, when a PR has broken status checks, or when you need local reproduction commands for CI failures.
$ install --global
skillsauthnpx skillsauth add bahayonghang/my-claude-code-settings 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 24, 2026, 8:10 AM36.9s6 files scanned
SKILL.md
- name:
- gh-fix-ci
- description:
- Debug and fix failing GitHub PR checks with GitHub CLI. Use when GitHub Actions checks fail, when a PR has broken status checks, or when you need local reproduction commands for CI failures.
- category:
- git-github-collaboration
- version:
- 1.2.0
- Verify
gh auth status. If unauthenticated, ask user to rungh auth login. - Identify PR using
gh pr view --json number,urlor$ARGUMENTS. If no PR is found on the current branch and no number was given, stop and ask the user to specify one. - If
rtkis available, preferrtk gh ...,rtk read, andrtk grepfor exploratory steps. Use rawghor the bundled script when another command needs machine-friendly JSON or uncompressed logs. - Run
python "$SKILL_DIR/scripts/inspect_pr_checks.py" --repo "." [--pr "$ARGUMENTS"] --jsonto collect failing checks, log snippets, and local reproduction hints. If the script exits non-zero, fall back to the manual workflow in references/BACKGROUND.md. - Branch on the result:
- All checks pass → report "all checks green" and stop.
- Checks still in progress → report running checks and suggest waiting, or offer to inspect already-failed ones.
- Only external provider failures (e.g. Buildkite) → report URLs and mark out-of-scope unless the user explicitly asks.
- GitHub Actions failures exist → continue to step 6.
- Summarize failures with: check name, the smallest useful log snippet (cap at 50 lines; if logs exceed this, extract only the error block), and the suggested local repro command.
- Propose a concise fix plan and request explicit approval before editing when the user asked only for diagnosis. Otherwise proceed to fix.
- Implement the approved fix and rerun the relevant local repro commands. If the local repro still fails, diagnose the new error and iterate (max 2 retries) before reporting back. After local success, re-run
gh pr checksto confirm.
References
- references/BACKGROUND.md for detailed workflow and manual fallbacks
- scripts/inspect_pr_checks.py for the automated check inspector
Related Skills
bahayonghang/code-refactor
development
VerifiedTrustedCommunity
Implement safe, behavior-preserving code refactors after inspecting the existing project. Use when the user asks to refactor code, split large files or modules, extract functions or methods, reduce duplicated logic, rename confusing classes/functions/variables, improve code comments, remove unused or dead code, or says 重构代码, 拆分模块, 提取方法, 减少重复代码, 优化命名, 优化注释, 删除未调用代码. For broad refactor requests, plan safe slices and wait for approval; for narrow scoped requests, directly implement the smallest verifiable slice.
15SKILL.mdUpdated Jun 6, 2026
bahayonghang/codex-dynamic-workflows
development
VerifiedTrustedCommunity
Use only when the user explicitly asks for swarm, subagents, parallel agents, dynamic workflow, multi-agent orchestration, 多智能体编排, or when the task truly needs coordinated research plus implementation plus review plus verification packets. Do not use for ordinary code review, planning-only work, single-line bugfixes, routine audits, or migrations unless orchestration is requested or at least two independent workflow dimensions are present.
15SKILL.mdUpdated Jun 4, 2026
bahayonghang/code-quality-review
development
VerifiedTrustedCommunity
Run a code quality review focused on maintainability, structure, abstraction quality, file growth, branching complexity, boundary cleanliness, and refactoring opportunities. Use when the user asks for code quality review, code review, maintainability review, architecture quality review, PR code quality feedback, 代码质量审查, 代码质量 review, 可维护性审查, 架构质量审查, or review comments about code structure. Do not use for pure security review, formatting-only review, performance profiling, or implementation tasks unless the user also asks for a code quality review.
15SKILL.mdUpdated Jun 4, 2026
bahayonghang/spark
development
VerifiedTrustedCommunity
Plan-first brainstorming workflow that turns an idea into an approved Markdown implementation plan by default. Use when the user wants to brainstorm, design, scope, or plan a feature/spec before implementation. Spark explores project context, asks only blocking questions, writes the plan under the project root's .plannings/YYYY-MM-DD-feature-slug.md path, self-reviews it, and waits for user approval. Create an HTML or visual plan/spec only when the user explicitly asks for HTML, browser-viewable, or visual output; save the paired .html beside the Markdown plan.
15SKILL.mdUpdated May 29, 2026