Skip to content

Starfie1d1272/dsh-github-skills / skills/gh-fix-ci

gh-fix-ci

Verified

Diagnose or fix failing GitHub Actions checks from real check and log evidence. Use when the user asks why CI failed or wants failing checks fixed; non-Actions CI is report-only.

GitHub Actions CI Fix

Diagnose or fix failing GitHub Actions checks on a pull request, from real check and log evidence. "Current branch" resolves to its associated PR; branch-only Actions runs without a PR are outside this workflow.

Evidence

  • Establish the root cause only from real check state, logs, and diff evidence; never fabricate a failure reason from a single error string.
  • Use a visible capability for PR metadata and checks when it is semantically sufficient; use a capability that exposes actual logs when available; otherwise use scripts/inspect-pr-checks.mjs or gh.
  • Non-Actions CI is report-only: check name + URL + state, never their logs.
  • Missing, pending, or inconclusive logs are uncertainty — report them as such, do not guess.

Workflow

  1. Resolve the PR (given number/URL, or current branch via local git context; ask if still ambiguous).
  2. Gather failing-check evidence (see Evidence) and summarize failures with run URLs and log snippets.
  3. Diagnose-only requests get a root cause and explanation only.
  4. Fix mode (only when the user asked to fix): apply the minimal local change tied directly to the root cause, run the most relevant local verification, then recheck the status. If the failure is clearly unrelated to the local diff, say so before proposing code changes.
  5. Report: evidence, root cause, changed files, verification run, and residual risk.

Remote write boundary

Local edits are allowed under "fix the CI" intent. Pushing, re-running a workflow, and commenting on the PR require explicit user request or the host approval boundary.

receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall