adev:bugfix-loop

An automated loop for working through eligible P2 and P3 software bugs from an issue board. It handles one bug per cycle and uses a systematic debugging workflow for each attempt.

In plain words
What is it for?
It is for unattended bug-triage and bug-fixing runs. It can select board issues, investigate each bug, attempt the work, and optionally pull from and write results back to GitHub.
Why use it?
It lets a project process a queue of lower-priority bugs without stopping for manual selection after every bug. Limits can cap the number of bugs or cycles, and optional GitHub synchronisation updates the issue tracker.

Skill for Claude CodeCodex

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 skills/agentic-development/adev-plugin/bugfix-loop
Any agent
npx skills add agentic-development/adev-plugin --skill bugfix-loop
Clone the repo
git clone --depth 1 https://github.com/agentic-development/adev-plugin

Made for: Claude Code, Codex.

Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,221 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.00055 $0.06221
Opus 5 $0.00028 $0.03111
Sonnet 5 $0.00011 $0.01244
Haiku 4.5 $0.00006 $0.00622

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

Security

Grade A, and why

adev:bugfix-loop 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 2d 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.

providers/codex/skills/bugfix-loop/SKILL.md · 249 lines

How it starts

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

Autonomous Bugfix Loop

Announce at start: "I'm using the adev:bugfix-loop skill to drain eligible bugs from the board."

Arguments

  • --max-bugs <N>: caps bugs attempted across the whole run (across all self-re-invoked turns). Default: unbounded — the loop drains until no eligible bug remains or --max-turns is hit.
  • --max-turns <N>: caps self-re-invocation turns. Default: 20 — a conservative bound preventing an unbounded run when neither flag is set.
  • --github-sync: enables the tracker-provider-bridge's inbound pull before each bug selection and outbound writeback after each attempt (tracker-provider-bridge.spec.md). Inbound sync runs once per turn in Step 0, before the status/budget guard; outbound writeback runs once per completed attempt in Step 4. Both degrade gracefully (never error the loop) when GitHub or gh is unreachable — see Failure Modes below.
  • --resume [--resume-run-id <id>] (internal): used only by this skill's own self-re-invocation, mirroring /adev:build --resume. Not intended for direct user invocation. --resume-run-id is always passed explicitly by the re-invocation call — the skill always knows its own run_id from the turn that just completed. A manual --resume without --resume-run-id falls back to adev bugfix-loop latest (the rare case of a manual --resume after a crash where the exact run_id wasn't captured).
  • --worktree-per-bug: default OFF. When set, each bug's claim, /adev:debug --auto attempt (Step 4), and any resulting commit happen inside a dedicated adev-managed worktree (adev worktree add --slug bugfix-<issue-id> --base <ref>) instead of the shared working tree — isolating each bug's diff from every other bug's in-flight changes (spec BEH-3).
  • --auto-commit: default OFF. When set (with or without --worktree-per-bug), a FIXED verdict triggers Step 4.5's commit/push/PR automation (spec BEH-4). Without either --worktree-per-bug or --auto-commit, Step 4.5 is skipped entirely and behavior is unchanged from before this capability existed.
  • --max-priority <P0-P4>: caps the priority band Step 2 selects from. Default: P3 (covering P2/P3, identical to today's hardcoded behavior). The full P0-P4 range is accepted — P0/P1 are a deliberate, explicit operator opt-in (BEH-9), not rejected the way they were before the eligibility-floor amendment shipped. Validated fail-fast at Step 0, before any bug selection (BEH-10); malformed values (anything other than P0-P4) halt the run with INVALID_PRIORITY_BOUND. BEH-7's unconditional module-exclusion floor (reserved safety tags, always enforced) is unaffected by this flag at any value, including P0 — it is the actual, non-configurable safety boundary, not the priority band.

Read the full file on GitHub · 249 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 249 lines · 55 tokens per session scan A 4e74c1480a38

Subscribe to this mod's changes

adev:bugfix-loop is a skill published in the GitHub repository agentic-development/adev-plugin (11 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 6,221 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens