A user-triggered workflow that reads open issues, claims them, fixes their causes, verifies the changes, and closes the issues when the fixes are complete.

Use it to repair open project issues, add regression tests for bugs, document fixes, and close verified issues.

It organizes issue repair so work is scoped, tracked, tested, and recorded.

fix — Command for Claude Code by daphnee-ovo/dev-flow

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/daphnee-ovo/dev-flow

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/daphnee-ovo/dev-flow/fix/github.svg)](https://agentmods.dev/commands/daphnee-ovo/dev-flow/fix)

Your own site

<a href="https://agentmods.dev/commands/daphnee-ovo/dev-flow/fix"><img src="https://agentmods.dev/badge/commands/daphnee-ovo/dev-flow/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/daphnee-ovo/dev-flow/fix"><img src="https://agentmods.dev/badge/commands/daphnee-ovo/dev-flow/fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 499 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.00009	$0.00499
Opus 5.5	$0.00004	$0.00200
Sonnet 5.5	$0.00002	$0.00100
Haiku 4.5	$0.00001	$0.00050

Measured 1mo ago against content hash 59887d0e512b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 1mo 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.

plugin/commands/fix.md · 67 lines

What it actually says

FIX — User-triggered automatic issue repair

Only run this workflow when the user explicitly invokes /fix. Do not invoke it automatically from hooks, /test, /check, task completion, or issue creation.

Execution

List open issues with dow issue list. The CLI resolves the active branch's document root. If there are no open issues, report that and stop.
Read each issue with dow issue show <ISSUE-ID> and understand its scope, reproduction steps, affected files, and any related task or specification.
Claim every issue before making project changes:
```
dow claim <ISSUE-ID>...
```
Fix each claimed issue. Locate the root cause, keep the change scoped to the issue, and run appropriate verification. Bug fixes require a regression test; if that is technically infeasible, explain the alternative verification and ask the user before closing the issue.
For a verified fix, record the result and close the issue:
```
dow issue update <ISSUE-ID> --fix "<concise fix summary>"
dow issue close <ISSUE-ID>
```
dow issue close checks the issue, renames a fully closed issue file, and revokes its claim. Do not edit the issue checkbox or rename issue files manually. If update or close fails, do not report the issue as fixed.
Leave unfixable issues open. Report the reason, verification performed, and the suggested next step.

Completion Report

Summarize every issue handled:

[dev-flow] Issue Fix Report
Fixed: N
Cannot fix: M
Blocked: K

Details:
  ✓ <issue-id>: <one-sentence fix and verification summary>
  ✗ <issue-id>: <reason and next step>
  ! <issue-id>: <claim or workflow blocker>

Audit Mode

When the mode is audit/<original_mode> (for example, audit/quick), the fix workflow is unchanged. After all issues are fixed, prompt the user to run /iterate; /iterate restores the original mode after completion.

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.

1mo ago First seen · 67 lines · 9 tokens per session scan A 59887d0e512b

Subscribe to this mod's changes

fix is a command published in the GitHub repository daphnee-ovo/dev-flow (2 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 499 once invoked, about $0.0000 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-08-31.

Claude Code Debugging ai-coding codex-cli coding-agent developer-tools hooks

fix

A troubleshooting workflow that first identifies the root cause, then proposes the smallest change, and finally explains how to verify it.

aiflowlearn/awesome-claude-code · 0 tokens

debugger

You are the Support & Debug persona in the ColdStart workflow. You are a relentless bug hunter who refuses to accept vague issues, half-documented bugs, or silent failures. You operate under these core assumptions: no error is random, no user report is exaggerated, and every failure is traceable to a flaw in logic…

samibs/skillfoundry · 0 tokens

diagnostico

Verificar la salud del setup de Don Cheli en el proyecto actual.

doncheli/don-cheli-sdd · 14 tokens

code-locate

Locate code paths and line ranges for a described behavior: up to 10 candidates with HIGH/MEDIUM/LOW confidence and a search trail, plus a proposed SOURCEOFTRUTH.md update. Use when the first question is where one specific behavior lives and paths are unknown. Do not use when paths are explicit, the codebase is tiny…

Mozurok/fhorja.dev · 0 tokens

cg-senior-code-review

Perform deep, findings-first senior engineering code reviews of any change in any language or stack. Use when reviewing a phase, feature branch, pull request, commit, or uncommitted changes for correctness bugs, security and abuse risks, regressions to existing behavior, concurrency and lifecycle defects, performance…

akinalpfdn/claude-ground · 97 tokens

cleanup

A cleanup command that finds code, files, and dependencies that appear to be unused, then removes only items confirmed to be unnecessary.

xiaobei930/cc-best · 7 tokens