/github-fix-ci

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select github-fix-ci from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv github-fix-ci, /just-vibe github-fix-ci and /jv:github-fix-ci in Claude. See shortcut setup and context examples.

What the agent does

1. Resolve the run ID, attempt, job and head SHA, and find the first causal failure.
2. Compare runner configuration and lockfiles, and reproduce locally with the relevant workspace and runtime before patching.
3. Patch the cause and validate it before an authorized rerun or push.
4. All changes are owned by the user. Add no agent/model self-attribution, AI-generated signature, badge, or agent Co-authored-by trailer to commits, PRs, comments, release notes or messages. Use the existing user Git identity; preserve legitimate human attribution and required third-party notices.
5. Use the matching bundled evidence collector when available; read its result and limitations rather than treating exit zero as readiness. Revalidate identity before a dependent action.

Inputs

• failed PR/check run and exact revision. Requires Actions logs and local checkout.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

Repair the identified CI failure; no weakening checks to make them green.

Writes

Apply: only the requested local changes and relevant isolated verification. Inspect/plan requests remain inspection/planning. External actions require their exact action and target in session authorization.

Mode

Apply; failed PR/check run and exact revision. Requires Actions logs and local checkout.

Prerequisites

Exact owner/repository and relevant issue/PR/ref; authenticated read access through an available connector or CLI for remote evidence. External writes require the requested operation, appropriate account permissions, and rechecking target state. Local preparation remains useful without write access.

Expected output

• Run/job/revision identity, causal log, focused fix with local evidence, and corrected-revision check status only if actually exercised.

How the work is checked

• A genuine test regression is fixed; an infrastructure outage is distinguished from code failure.
• Review newly prepared commit/PR/message text, including template or hook additions, for agent self-attribution before submission; verify the resulting artifact when available. Do not silently rewrite existing history or remove human credits.

When to stop or clarify

• Do not expose log secrets or loop costly reruns. Green status must refer to the corrected revision.

Handling missing context

Infer

Resolve owner/repository and PR/issue/ref from links, remotes and supplied artifacts; inspect available account and head identity.

Assume

Prepare local text or analyze supplied evidence if remote access is absent; label its freshness.

Ask

Ask only when repository/account/target ambiguity blocks the requested remote action; missing write access does not block local drafting.

Technical guidance

Evidence

Read the first failing step and run attempt at the relevant SHA; compare matrix OS, toolchain, event and permissions.

Method

Reproduce the smallest matching environment; distinguish test failure from billing, quota, provisioning or credential failure.

Pitfall

Re-running unchanged code cannot repair an account spending limit; hiding a matrix entry discards coverage.

Check

Verify a new relevant run on the changed SHA, or explicitly retain pending remote evidence when local checks are all that ran.

Situational decisions

When failure is external or a required secret is withheld on forks: Report the environment cause and safe alternative; do not grant fork code privileged tokens.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring