What is fix-and-retry?

A workflow for handling a failed continuous-integration run from diagnosis through a new verification run. Continuous integration, or CI, automatically builds and tests code after changes.

Use it when CI fails and you want to inspect the error, fix the affected code, commit and push the change, and monitor the replacement run.

It groups the investigation, code fix, commit, push, and monitoring steps into one repeatable process. It also checks that the watched run belongs to the new commit.

fix-and-retry — Skill for Claude Code by urmzd

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.

Any agent

npx skills add urmzd/dotfiles --skill fix-and-retry

Clone the repo

git clone --depth 1 https://github.com/urmzd/dotfiles

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/urmzd/dotfiles/fix-and-retry.svg)](https://agentmods.dev/skills/urmzd/dotfiles/fix-and-retry)

Your own site

<a href="https://agentmods.dev/skills/urmzd/dotfiles/fix-and-retry"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/fix-and-retry.svg" alt="Measured on agentmods" height="20"></a>

Per session 106 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 662 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00106	$0.00662
Opus 5	$0.00053	$0.00331
Sonnet 5	$0.00021	$0.00132
Haiku 4.5	$0.00011	$0.00066

Measured 7d ago against content hash 890abff39c2b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

fix-and-retry 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 7d 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.

dot_agents/skills/fix-and-retry/SKILL.md · 44 lines

How it starts

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

Fix and Retry

Diagnose CI failure, fix it, and re-ship.

Steps

Diagnose: Follow the diagnose-ci workflow:
- gh run list --status=failure --limit 1 --json databaseId,name,headBranch to find the latest failure
- gh run view <id> --log-failed to get error logs
- Identify root cause and affected files
Fix: Apply the fix to the codebase. Read the affected file(s), make the edit, and verify the fix makes sense.
Commit: Create a conventional commit for the fix (e.g., fix(ci): correct workflow syntax). Use a HEREDOC for the message.
Push: Before pushing, capture the pre-push run id (gh run list --branch $(git branch --show-current) --limit 1 --json databaseId -q '.[0].databaseId'). Then git push.
Watch: Poll for a NEWER run, not the previous failed one. Match the new run by the pushed commit's headSha (git rev-parse HEAD) -- e.g. gh run list --branch $(git branch --show-current) --limit 5 --json databaseId,headSha,status,conclusion and pick the run whose headSha equals the new HEAD (and whose id differs from the captured pre-push id). Poll every 15s (max 5 minutes) until that run completes. This prevents the watcher from latching onto the previous failed run before the new run is registered.
Report: Show whether the re-run passed or failed. If it failed again, show the new error.

Rules

Only fix issues you can confidently diagnose from the logs. If the cause is unclear, report the diagnosis and ask the user rather than guessing.
Never force push or amend the previous commit.
If the fix requires secrets, env vars, or manual GitHub settings changes, explain what's needed instead of attempting it.

Gotchas

A new CI run is not registered the instant you push. Capture the pre-push run id (step 4) and poll for a run whose headSha matches the newly pushed HEAD before reading status. If you watch --limit 1 blindly, the watcher can latch onto the previous failed run and report a false failure.

Read the full file on GitHub · 44 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.

7d ago First seen · 44 lines · 106 tokens per session scan A 890abff39c2b

Subscribe to this mod's changes

fix-and-retry is a skill published in the GitHub repository urmzd/dotfiles (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 106 tokens to every session and 662 once invoked, about $0.0005 per session on Opus 5. 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.

CI and CD Debugging DevOps and cloud chezmoi dotfiles neovim nvim tmux zsh

save-debug-experience

Record a debugging session's findings into a timestamped markdown file under debugexperience/. Captures problem, root cause, solution, and key learnings in a structured, reusable format. Use when: you've just resolved a non-obvious bug, found an undocumented edge case, encountered an issue that took multiple attempts…

magic3007/dotfiles · 113 tokens

use-codefresh

Reference for using Codefresh via the CodeFresh CLI. Use when a Codefresh CI check is failing in a recursionpharma PR, or when working with Codefresh builds.

ooloth/dotfiles · 39 tokens

use-next-devtools

Reference for using the NextJS Dev Tools via the nextjs-agent. Use to debug or observe Next.js framework internals.

ooloth/dotfiles · 30 tokens

prisma-connection-pool-exhaustion

Fix Prisma "Too many connections" and connection pool exhaustion errors in serverless environments (Vercel, AWS Lambda, Netlify). Use when: (1) Error "P2024: Timed out fetching a new connection from the pool", (2) PostgreSQL "too many connections for role", (3) Database works locally but fails in production…

magic3007/dotfiles · 100 tokens

typescript-circular-dependency

Detect and resolve TypeScript/JavaScript circular import dependencies. Use when: (1) "Cannot access 'X' before initialization" at runtime, (2) Import returns undefined unexpectedly, (3) "ReferenceError: Cannot access X before initialization", (4) Type errors that disappear when you change import order, (5) Jest/Vitest…

magic3007/dotfiles · 88 tokens

nextjs-server-side-error-debugging

Debug getServerSideProps and getStaticProps errors in Next.js. Use when: (1) Page shows generic error but browser console is empty, (2) API routes return 500 with no details, (3) Server-side code fails silently, (4) Error only occurs on refresh not client navigation. Check terminal/server logs instead of browser for…

magic3007/dotfiles · 87 tokens