A guided bug-fixing workflow that investigates an issue, checks the relevant code and documentation, applies a fix, verifies it locally, and prepares a pull or merge request.

Use it to analyze tickets, find root causes, implement fixes, run local checks, and deliver reviewable changes.

It connects scattered issue details and code evidence so bugs can be traced from report to verified correction.

dev-fix — Command for Claude Code by HoangNguyen0403

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.

Clone the repo

git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

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/commands/hoangnguyen0403/agent-skills-standard/dev-fix/github.svg)](https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/dev-fix)

Your own site

<a href="https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/dev-fix"><img src="https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/dev-fix/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/commands/hoangnguyen0403/agent-skills-standard/dev-fix"><img src="https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/dev-fix.svg" alt="Reviewed on agentmods" width="80" 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,488 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.00000	$0.01488
Opus 5	$0.00000	$0.00744
Sonnet 5	$0.00000	$0.00298
Haiku 4.5	$0.00000	$0.00149

Measured 8d ago against content hash 04488156e14b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

dev-fix 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 8d 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.

.claude/commands/dev-fix.md · 171 lines

How it starts

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

Dev Fix

Unified developer workflow for fixing bugs. Analyzes issue-tracker context, cross-checks docs/code, proposes a solution, implements the fix, verifies locally, and delivers a PR/MR.

Input: $ARGUMENTS

Instructions

Execute the following steps for $ARGUMENTS.

Dev-Fix — Bug Remediation

Goal: Take a bug ticket from root-cause analysis through a locally-verified PR/MR, enforcing a strict Propose -> Approve -> Verify cycle.

Input

/dev-fix <issue-url-or-key>

Workflow

Step 0: Environment Prep (Turbo)

// turbo

Sync Registry: git pull origin main in the standard repo.

Step 1: Research & Discovery (Implementation Plan Phase)

[!TIP] Sub-Agent Delegation: If your platform supports sub-agents, delegate ticket extraction to specialist-jira-analyst and context lookup to specialist-codebase-scout. If sub-agents are NOT supported, execute these steps yourself.

Analyze Ticket: Use installed Jira/GitHub/GitLab/ADO MCP first; otherwise use exported ticket text. Extract Reproduce steps, Expected Result, and Actual Result.
Cross-Check Context: Use knowledge-base MCP when configured; otherwise use local code search. Locate relevant code.
Create Implementation Plan:
- Use the Implementation Plan Template below.
- Initialize project-local docs/prd/prd-plan-[slug].md.
- Goal: Clear description of the root cause.
- Proposed Changes: Exact files and logic to be modified.
- Verification Plan: Detail which QE skill will be used to verify the fix locally before PR.
- Do not propose code changes until repro steps, expected result, and root cause hypothesis are explicit.
HARD STOP: Request user approval for the implementation plan.
Readiness Gate: Run implementation-readiness; code only after READY or approved PARTIAL.

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

8d ago First seen · 171 lines · 0 tokens per session scan A 04488156e14b

Subscribe to this mod's changes

dev-fix is a command published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,488 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-09-03.

Debugging Git and workflow React best-practices coding-standards flutter nestjs nextjs

dev-fix