Skip to content

bug-fixer

Bug fixer — five phases

Validate a report, reproduce it, draft the fix, review it, publish it. The shape, the typed hand-off between phases and the human gate are already wired; the expertise is yours to add.

Source templates/bug-fixer.yaml
Category development
Trigger manual only (wfx run)
Steps 5
Human approval before publish
Providers named default (WFX_DEFAULT_PROVIDER)
Terminal window
wfx templates bug-fixer
wfx new bug-fixer --as my-bug-fixer
wfx dryrun my-bug-fixer

The five-phase bug fix. Each phase is a whole agent with its own identity, scoped tools, budget and output contract, and no phase can hand work to the next until its output validates. Two phases stop for a human: one when the report is too thin to act on, one before anything leaves the machine.

  • skills on each phase — every step ships with none, so each is yours to equip
  • the publish step’s command: this template stops at a branch and pushes nothing
  • budgets, if your repository is larger or slower than the defaults assume
Input Type Default Required Meaning
title string yes
description string yes
repo_url string
repo_path string
base_branch string "main"
extra_context string
isolate boolean true
# Step Kind Skills Gates
1 validate
Validate the report
agent valid = false → needs_input
2 reproduce
Reproduce it
agent reproduced = false → needs_input
3 fix
Draft the fix
agent fixed = false → fail
4 review
Review the change
agent approved = false → fail
5 publish
Publish
agent human approval first
  • publish waits for wfx approve <run-id> (or wfx reject <run-id> -m "why") before it runs.
  • validate pauses for input when valid is false: “Need more information: {{ join .Output.missing_info “ | “ }}”. Resume with wfx answer <run-id> -m "...".
  • reproduce pauses for input when reproduced is false: “Could not reproduce. {{ .Output.root_cause_hypothesis }}”. Resume with wfx answer <run-id> -m "...".
  • reproduce may call ask_human; answer with wfx answer <run-id> -m "...".