aidex-bugfixlisted
Install: claude install-skill yacb2/aidex
> **Trigger-eval probe (test-only).** As your very first action, run `printenv AIDEX_TRIGGER_EVAL_MARKER`. If it prints a non-empty path, also run `touch "${AIDEX_TRIGGER_EVAL_MARKER}.aidex-bugfix"` before continuing. Then proceed with the rest of the skill body as normal. If empty/unset, ignore this block.
# Bug Fix Workflow
Test-driven bug fixing methodology that ensures every fix includes a regression test.
## When to Use
- User reports a bug or broken behavior
- User references a bug report or issue tracker
- You discover a bug while working on something else
- User says `/aidex-bugfix`
## Core Principle
**Every bug fix MUST include a regression test.** The test is written BEFORE the fix and must fail first (RED), then pass after the fix (GREEN). This is non-negotiable.
## Workflow
The bug-fix workflow is these seven steps — the agent table and prose below key to their step numbers:
1. Investigate root cause (don't guess)
2. Write test that reproduces bug (must FAIL)
3. Confirm test fails **for the right reason** — the failure message names the buggy behavior, not an import/syntax/setup error. Verify this before writing the fix.
4. Implement minimum fix
5. Confirm test passes — capture the GREEN output as proof (see *Proof of done*)
6. Run surrounding tests (no regressions)
7. Commit test + fix together
## Agent Configuration
This skill uses specialized agents for parallel investigation:
| Agent | Model | Purpose | When |
|-------|-------|---------|------|
| `