factory-issue-fixlisted

The software factory engine — turn ONE GitHub issue into a reproduced, diagnosed, independently-verified, fixed DRAFT PR. Reproduce (a bug that will not reproduce is never fixed) → Diagnose (root cause + narrowest boundary) → Verify (an INDEPENDENT model family decides real bug vs intended behaviour) → Fix (worktree-isolated, fixture-first, draft PR only). Self-bootstraps from the factory queue when given no issue; never merges and never pushes main. Use when you want one bug driven from unverified report to reviewable draft PR unattended — run the factory on this, fix this issue end to end. Not for choosing which issues to fix (use issue-triage-fanout), not for a straightforward already-diagnosed issue (use implement-issue, or stacked-impl-lanes for a wave of them), and not for landing the PR it produces (use factory-land).
schmug/shipofclaudius · ★ 0 · Code & Development · score 56

Install: claude install-skill schmug/shipofclaudius

Run the `factory-issue-fix` dynamic workflow bundled with this plugin by calling the Workflow tool with its bundled script path: ``` Workflow({ scriptPath: "${CLAUDE_PLUGIN_ROOT}/.claude/workflows/factory-issue-fix.js", args: { issue: 123, repo: "owner/name" } }) ``` **No args are required.** With no `args.issue` the workflow gathers its own queue read-only (`gh issue list --label factory --label needs-repro`) and advances the oldest candidate, so a bare `Workflow({ name: "factory-issue-fix" })` from a cron or Action driver works. An empty queue is a clean no-op, not an error. Other args: `repo?`, `base?` (default `main`), `branch?` (default `factory/issue-<N>`), `startAt?` / `stopAfter?` (`reproduce` | `diagnose` | `verify` | `fix` — advance one phase per run and resume from the committed `report.md`), `prior?` / `priorReport?` (hand the previous run's return or report back in on resume), `diagnoseModel?` (default `opus`), `verifyModel?` (default `sonnet`), `confidenceThreshold?` (default `2/3`), `fresh?`, `readonlyAgent?` (default `Explore`). For the full, current list read the header comment / `meta` block in `${CLAUDE_PLUGIN_ROOT}/.claude/workflows/factory-issue-fix.js`, or the repo README "Arguments" table. **The Verify phase must run on a different model family from Diagnose** — passing the same value for both throws. A same-model verifier agrees with itself, and independence is the entire value of the phase. **Its Fix phase WRITES** — it commits a fixture, pushes