22 lines
1.2 KiB
Markdown
22 lines
1.2 KiB
Markdown
---
|
|
name: fix-pipeline
|
|
description: "Diagnoses, fixes, and verifies bugs across Architect, Developer, Tester, and Writer."
|
|
---
|
|
|
|
## What I do
|
|
|
|
I resolve bugs by triaging ownership, applying code fixes, and running regression tests:
|
|
|
|
1. **Architect (Triage)**: Compares the bug report against existing `specs/` and codebase architecture.
|
|
- **Spec / Design Defect**: Updates `specs/` and `decisions.md`, then forwards to `@developer`.
|
|
- **Implementation Defect**: Forwards directly to `@developer` without updating specs.
|
|
2. **Developer**: Applies surgical code fixes adhering to Godot performance and typing rules.
|
|
3. **Tester**: Writes a GUT regression test, executes test suites, and verifies the fix (max 2 repair attempts).
|
|
4. **Writer** (Conditional): Updates README or API docs if external interfaces or setup instructions changed.
|
|
|
|
## Execution Rules
|
|
|
|
- Default to starting at Step 1 (`@architect`) for triage unless explicitly told `--dev-only`.
|
|
- Allow `@tester` a maximum of 2 auto-repair attempts for failing test suites before passing back to `@developer`.
|
|
- Stop and ask the user for clarification if any step fails or is ambiguous.
|
|
- Pass context from each completed stage to the next stage. |