just-vibeGeneral · inspect by default
/ci
Diagnose or improve continuous integration
Use for CI diagnosis across providers; github-fix-ci handles GitHub run identity and requested repairs.
Make it your own.
In Claude Code, use the slash command and add your context. In Codex, select ci from the just-vibe skill picker, then send the same brief.
Version 0.11.0 also supports /jv ci, /just-vibe ci and /jv:ci in Claude. See shortcut setup and context examples.
/just-vibe:ci Diagnose the failed matrix job from these logs without rerunning it./just-vibe:ci Fix the Jenkins pipeline's failing Node 24 matrix stage without disabling the other stages./just-vibe:ci Inspect supplied CI logs without runner access or triggering a rerun.What the agent does
- Find the first causal failure in the job graph, distinguishing required failures from downstream cancellations.
- Compare effective runner and local runtime and lockfile inputs to separate a code failure from an infrastructure failure.
- Validate authorized workflow changes.
Inputs
- workflow files and relevant runner logs.
Optional context: scope, references, constraints, successCriteria, environment, mode, budget.
Scope
- Reads
- Repository CI behavior; GitHub-specific operations use the GitHub pack.
- Writes
- Inspect/plan: inspect or propose; save requested artifacts only. Apply: edit the requested local implementation and perform relevant bounded checks while preserving unrelated work. Live data changes, remote actions and paid jobs require their resolved target and existing session authorization.
- Mode
- Inspect for diagnosis; apply for requested fixes. Requires workflow files and relevant runner logs.
- Prerequisites
- Resolve the user brief and inspect the relevant project or supplied evidence. External capabilities are optional unless the selected action actually needs them.
Expected output
- Run/revision identity, causal log excerpt and environment difference, with a focused patch and local checks when a fix was requested, and remaining remote verification.
How the work is checked
- A cache-related failure is not hidden by ignoring errors; unrelated matrix jobs remain intact.
When to stop or clarify
- Do not rerun costly jobs or change organization secrets without the relevant request. Report inaccessible logs explicitly.
Handling missing context
- Infer
- Resolve the named files, existing scripts, current task and earlier corrections from the conversation and repository.
- Assume
- Use the narrowest interpretation that completes a reversible local task; state a consequential assumption once.
- Ask
- Ask when competing targets or incompatible success conditions would change the result; continue independent inspection first.
Technical guidance
- Evidence
- Inspect run identity, first causal failure, matrix, caches, tool versions and event permissions.
- Method
- Reproduce the failing boundary and preserve unrelated coverage; route GitHub-specific trust issues to its Actions guide.
- Pitfall
- Disabling tests or broadening secrets access can make CI green while weakening correctness or security.
- Check
- Run the relevant local check as bounded local execution and verify a matching remote run when available, distinguishing infrastructure blockers from code defects; use existing logs when no local run is possible.
Situational decisions
When logs show a provider outage rather than changed-code failure: Preserve evidence and recommend a bounded rerun without weakening checks.
The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.