bahayonghang/gh-fix-ci
content/skills/git-github-skills/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 3, 2026, 7:25 PM6.3s5 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
- version:
- 1.1.0
- Verify
gh auth status. If unauthenticated, ask user to rungh auth login. - Identify PR using
gh pr view --json number,urlor$ARGUMENTS. - 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. - Summarize GitHub Actions failures with check names, the smallest useful log snippet, and the suggested local repro commands. Mark external providers (for example Buildkite) as out-of-scope unless the user explicitly asks for them.
- 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, rerun the relevant local repro commands, then re-run
gh pr checksto verify.
References
See references/BACKGROUND.md for detailed workflow and manual fallbacks.
Related Skills
bahayonghang/goal-meta-skill
development
VerifiedTrustedCommunity
Turn vague or complex Codex tasks into strong `/goal` commands with outcome, verification, constraints, boundaries, iteration policy, completion evidence, and pause/block conditions. Use when the user asks for Codex goal instructions, Goal 指令, 目标指令, `/goal` prompts, 中文 Goal 模板, plan-to-goal interviews, success criteria, verification commands, or bounded agent work definitions.
15SKILL.mdUpdated Jun 13, 2026
bahayonghang/ast-grep
tools
VerifiedTrustedCommunity
Write, debug, and validate ast-grep structural code search rules. Use this skill when the user needs syntax-aware code search, AST pattern matching, structural refactor discovery, language-construct queries, or searches that plain text tools like rg can miss, such as finding functions with particular descendants, calls inside specific contexts, missing error handling, React hook shapes, decorators, or other Tree-sitter-backed code structures.
15SKILL.mdUpdated Jun 9, 2026
bahayonghang/goudi
development
VerifiedTrustedCommunity
Use when the user asks to ground an ambitious proposal, avoid over-grand designs, make a bold direction executable, pressure-test feasibility, prevent "too much vision and too little landing", or turn a strategy/refactor/product idea into the smallest verifiable first move with stop rules. Trigger for requests such as 落地, 先落地, 别太飘, 收一收, 可执行, 可验证, 止损, and for follow-ups after geju-style big-picture thinking. Do not trigger for ordinary code review or implementation unless the user explicitly asks to ground or shrink the plan first.
15SKILL.mdUpdated Jun 7, 2026
bahayonghang/geju
development
VerifiedTrustedCommunity
Use when the user explicitly asks to think bigger, open up the design space, challenge conservative design, avoid over-indexing on backward compatibility, escape local-detail fixation, or make a bold high-level product or architecture direction call. Use for strategic reframing, not for ordinary code review, PRD writing, implementation planning, or adversarial risk review.
15SKILL.mdUpdated Jun 7, 2026