shipshitdev/gh-fix-ci
bundles/github/skills/gh-fix-ci/SKILL.md
Diagnoses failing GitHub Actions checks on a PR, identifies root cause, and proposes or applies targeted fixes. Triggers when the user asks to fix CI, diagnose failing checks, fix a failing workflow, address GitHub Actions errors, or get a green build.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library 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: Jun 13, 2026, 5:18 AM8.8s2 files scanned
SKILL.md
- name:
- gh-fix-ci
- description:
- >-
- disable-model-invocation:
- true
- version:
- 1.0.0
- tags:
- github, ci, actions
GH Fix CI
Use this skill to diagnose failing GitHub Actions checks on a PR and propose a fix plan.
Contract
Inputs:
- Current branch or PR URL/number
- Optional failed run ID or job ID
Outputs:
- Failed check summary
- Root cause and impacted files
- Fix plan or applied local fix summary
Creates/Modifies:
- Local code/config changes only when the fix is clear or explicitly requested
- Does not rerun CI without approval
External Side Effects:
- Reads GitHub PR checks and Actions logs
- May rerun workflows only after approval
Confirmation Required:
- Before rerunning workflows
- Before pushing
- Before changing broad CI/deployment configuration
Delegates To:
testing-cicd-initwhen baseline CI is missingdeployment-composerwhen failures block a releasecode-reviewfor risky fixes
Workflow
- Verify auth:
gh auth status -h github.com
- Identify the PR:
gh pr view --json number,title,url- If no PR is found, ask for the PR URL.
- List checks:
gh pr checks
- For GitHub Actions failures, fetch logs:
gh run view <run-id> --log- If you only have a job id:
gh run view --job <job-id> --log
- Summarize the root cause and impacted files.
- Propose a fix plan and get user approval before changing code.
- For external checks (non-GitHub Actions), report the details URL and mark as out of scope.
Notes
- Do not rerun CI unless the user asks.
- Keep the failure summary concise and actionable.
Related Skills
shipshitdev/worktree
development
VerifiedTrustedCommunity
Create an isolated git worktree from the correct base branch and check it out into a clean, gitignored directory. Use when the user asks to make a worktree, spin up a parallel/isolated workspace, work on something without disturbing the current checkout, branch off the current work, or run multiple agents on the same repo at once. Picks the base branch smartly — the current feature branch when you are on one, otherwise the develop integration branch — so worktrees continue your in-progress work by default instead of forking from the wrong place.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/release-cleanup
development
VerifiedTrustedCommunity
Verify a release was fully promoted through develop, staging, and master/main, then prune merged local and remote branches and stale git worktrees. Squash-merge aware — uses GitHub PR merge state as the merge oracle, not commit ancestry. Use when the user asks to clean up branches after a deploy, prune worktrees, remove merged branches, tidy up after promoting develop to staging to master, or confirm nothing stale was left behind before pruning.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/finishing-a-development-branch
development
VerifiedTrustedCommunity
Structured "done coding, now what?" workflow: verify tests pass, detect the repository environment (normal repo vs worktree, named branch vs detached HEAD), present exactly the right merge / PR / keep / discard options, and execute the chosen path including safe worktree cleanup. Use when implementation is complete and the branch needs to be integrated, published, or abandoned.
27SKILL.mdUpdated Jun 13, 2026
shipshitdev/feature-intake
tools
VerifiedTrustedCommunity
Capture a client or stakeholder feature request, turn it into a planner-ready PRD epic with scoped sub-issues, check for duplicate work, and place approved issues on a GitHub Projects kanban. Use when a user invokes feature intake, asks to turn a rough client requirement into GitHub issues, or wants an idea written as a PRD and pushed to a board.
27SKILL.mdUpdated Jun 13, 2026