A user-run process for diagnosing and fixing software bugs, from small hotfixes to larger debugging sessions. It traces symptoms to the underlying cause and uses TDD, or test-driven development, where tests guide the change.

Use it for production issues, review findings, deployment regressions, flaky tests, and other known bugs.

It provides a structured way to find the cause instead of only treating the visible symptom. It also helps check that fixes do not create regressions, which are old problems that return after a change.

bugfix — Skill for Claude Code by irahardianto/awesome-agv

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 irahardianto/awesome-agv --skill bugfix

Clone the repo

git clone --depth 1 https://github.com/irahardianto/awesome-agv

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/irahardianto/awesome-agv/bugfix/github.svg)](https://agentmods.dev/skills/irahardianto/awesome-agv/bugfix)

Your own site

<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/bugfix"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/bugfix/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/bugfix"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/bugfix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 689 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.00044	$0.00689
Opus 5.5	$0.00018	$0.00276
Sonnet 5.5	$0.00009	$0.00138
Haiku 4.5	$0.00004	$0.00069

Measured 5d ago against content hash b292eea1bd2f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bugfix 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 5d 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.

.agents/skills/bugfix/SKILL.md · 73 lines

How it starts

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

Bug-Fix Skill

Entry-point guard: This is a user-invoked command skill (/bugfix). If you are a spawned subagent, do NOT execute this skill — return to your assigned scope card.

Purpose

Fix bugs of any size — from one-line hotfixes to multi-file debugging sessions — without the overhead of a full feature workflow.

When to Use

Bug fixes (any size, any complexity)
Hotfixes for production issues
Addressing review findings from /audit
Regression fixes after deployments
Flaky test fixes

When NOT to Use

New features (use /workflow-solo)
Refactoring (use /refactor)
Code quality audits (use /audit)

Pre-Implementation Checklist

Before starting, you MUST:

Scan .agents/rules/ directory for applicable rules
Read rule-priority.md for conflict resolution

Phases

Phase 1: Diagnose

Set Mode: Use task_boundary to set mode to PLANNING

Identify the bug or issue
Locate the affected code — trace from symptoms to root cause
If the cause is not immediately obvious, activate the Debugging Protocol skill
Assess blast radius — which files, features, and tests are affected?
Define the fix in task.md

Skills to consider:

Debugging Protocol — for non-obvious root causes, flaky tests, or multi-component bugs
Sequential Thinking — when multiple hypotheses need systematic evaluation

Phase 2: Fix + Test (TDD)

Set Mode: Use task_boundary to set mode to EXECUTION

Write a failing test that reproduces the bug
Apply the fix to make the test pass
Verify existing tests still pass
If the fix touches integration boundaries (database queries, API calls, external services), write or update integration tests
Follow applicable rules:
- Error Handling Principles @error-handling-principles.md
- Logging and Observability Mandate @logging-and-observability-mandate.md

Phase 3: Verify + Ship

Set Mode: Use task_boundary to set mode to VERIFICATION

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

5d ago First seen · 73 lines · 44 tokens per session scan A b292eea1bd2f

Subscribe to this mod's changes

bugfix is a skill published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 5d ago), licensed MIT. It adds 44 tokens to every session and 689 once invoked, about $0.0002 per session on Opus 5.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-10-15.

Debugging TDD Testing ai-agent ai-coding best-practices coding-standards framework generative-ai

legacy-code-changes

Making safe changes in unfamiliar, undertested, or legacy codebases — comprehension before modification, characterization tests, seams, and incremental replacement. Use when working in a codebase you didn't write, inheriting a project, touching code with no tests, planning a refactor of old code, or when the user says…

05-deepak-patidar/claude-skills · 95 tokens

om-troubleshooter

Diagnose and fix standalone Open Mercato bugs across scope, commands, locking, fields, generated registries, UI hydration, cache/search, bootstraps, queues, and providers. Use for "fix bug", "why does this fail", "regression", "debug", "napraw błąd", or a failing test.

open-mercato/open-mercato · 73 tokens

bugfix