fix-ci

fix-ci is a command for coding agents from rios0rios0/guide. It costs 0 tokens per session (1,630 once invoked), scanned A, original, MIT.

A command that finds the current GitHub pull request, reads its failed CI logs, fixes the underlying problems, and pushes one commit. CI is the automated system that builds and tests code for a pull request.

In plain words
What is it for?
Use it when a pull request's automated checks fail and you want the command to inspect logs, implement fixes, verify them, commit, and push.
Why use it?
It brings the failure investigation and repair into one workflow instead of requiring manual log hunting and branch checks.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/rios0rios0/guide/fix-ci
Clone the repo
git clone --depth 1 https://github.com/rios0rios0/guide

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for fix-ci

README.md
[![agentmods](https://agentmods.dev/badge/commands/rios0rios0/guide/fix-ci.svg)](https://agentmods.dev/commands/rios0rios0/guide/fix-ci)
Your own site
<a href="https://agentmods.dev/commands/rios0rios0/guide/fix-ci"><img src="https://agentmods.dev/badge/commands/rios0rios0/guide/fix-ci.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,630 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01630
Opus 5 $0.00000 $0.00815
Sonnet 5 $0.00000 $0.00326
Haiku 4.5 $0.00000 $0.00163

Measured 3d ago against content hash 8bbe03ff74fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fix-ci scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/workflows/generate-ai-rules/commands/fix-ci.md · 161 lines

How it starts

The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Detect the current branch's pull request, retrieve its failing CI workflow logs, fix the root causes, commit, and push. This command auto-detects the PR from the current Git branch, fetches check run statuses, downloads failure logs, classifies each failure, implements fixes, and pushes a single commit.

For commit conventions, refer to the Git Flow rule. For lint verification, refer to the CI/CD rule.

Pre-flight

Step 1 -- Verify GitHub CLI authentication

gh auth status

If this fails, report the error and stop. The gh CLI must be installed and authenticated.

Step 2 -- Detect repository context

gh repo view --json nameWithOwner -q '.nameWithOwner'

Split the result into {owner} and {repo}.

Step 3 -- Auto-detect PR from current branch

gh pr view --json number,headRefName -q '.number'

This returns the PR number associated with the current branch. If it fails (no PR exists for the current branch), report: "No pull request found for the current branch. Switch to a branch with an open PR or create one first." and stop.

Store the returned number as {PR_NUMBER}. Then ensure the local branch is up to date:

git pull --rebase

Procedure

Step 4 -- Fetch check run statuses

List all check runs for the PR and identify failures:

gh pr checks {PR_NUMBER}

Filter to checks with fail status. If no failing checks exist, report "All CI checks are passing on PR #{PR_NUMBER}." and stop.

Step 5 -- Retrieve failure logs

For each failing check, retrieve the workflow run ID and job ID from the check URL, then download the failed job logs:

gh run view {RUN_ID} --job {JOB_ID} --log-failed

If the log output is very large, use tail -100 to focus on the error section. Extract:

  • The specific error messages and file/line references
  • The tool or stage that failed (e.g., golangci-lint, make test, basic-checks)
  • Whether the failure is in code you can fix or an infrastructure/flaky issue

Read the full file on GitHub · 161 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 161 lines · 0 tokens per session scan A 8bbe03ff74fe

Subscribe to this mod's changes

fix-ci is a command published in the GitHub repository rios0rios0/guide (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,630 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.