Name: fix-bug
Author: zz-plant

Prompt file imported from zz-plant/stims (.github/prompts/fix-bug.prompt.md). Copyright stays with the author.

Fix a Bug

You have a bug to fix. Follow this flow to debug systematically.

1. Reproduce and Understand

Bug is reproducible (use ?agent=true URL if visual)
Understand: Is this runtime behavior, preset loading, or UI?
Check console/DevTools for errors
Identify: Which system is affected? (core, milkdrop, bootstrap, etc.)

2. Write a Failing Test

Before fixing, write a test that reproduces the bug:

# Add test to tests/path/to/spec.test.ts
# It should fail initially

bun run test tests/path/to/spec.test.ts

The test failing confirms you've reproduced the issue.

3. Fix the Bug

Edit the relevant source file (check Task Router if unsure)
Keep changes minimal and focused
Verify the test now passes:

bun run test tests/path/to/spec.test.ts

4. Verify No Regressions

# Quick check
bun run check:quick

# Test the area you modified
bun run test:integration  # if runtime/behavior
bun run test:compat       # if preset-related

# Visual verification (if UI-related)
bun run dev
# Test at: http://localhost:5173/milkdrop/?agent=true

5. Full Validation

bun run check

6. Update Session Context

Edit /memories/session/stims-context.md:

Root cause identified
Files changed
Test file path
Reproduction steps verified

7. Commit & PR

Commit message: Sentence case (e.g., "Fix preset loading race condition")
Include: root cause in description, step to reproduce, verification in the PR

Getting stuck? See:

Runtime issues: .agent/skills/verify-visualizer-work/SKILL.md → Testing section
Visual issues: docs/agents/visual-testing.md → Troubleshooting
Architecture: docs/ARCHITECTURE.md

Install fix-bug and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "prompt": "# Fix a Bug\n\nYou have a bug to fix. Follow this flow to debug systematically.\n\n## 1. Reproduce and Understand\n\n- [ ] Bug is reproducible (use `?agent=true` URL if visual)\n- [ ] Understand: Is this runtime behavior, preset loading, or UI?\n- [ ] Check console/DevTools for errors\n- [ ] Identify: Which system is affected? (core, milkdrop, bootstrap, etc.)\n\n## 2. Write a Failing Test\n\nBefore fixing, write a test that **reproduces the bug**:\n\n```bash\n# Add test to tests/path/to/spec.test.ts\n# It should fail initially\n\nbun run test tests/path/to/spec.test.ts\n```\n\nThe test failing confirms you've reproduced the issue.\n\n## 3. Fix the Bug\n\n- [ ] Edit the relevant source file (check Task Router if unsure)\n- [ ] Keep changes minimal and focused\n- [ ] Verify the test now passes:\n\n```bash\nbun run test tests/path/to/spec.test.ts\n```\n\n## 4. Verify No Regressions\n\n```bash\n# Quick check\nbun run check:quick\n\n# Test the area you modified\nbun run test:integration # if runtime/behavior\nbun run test:compat # if preset-related\n\n# Visual verification (if UI-related)\nbun run dev\n# Test at: http://localhost:5173/milkdrop/?agent=true\n```\n\n## 5. Full Validation\n\n```bash\nbun run check\n```\n\n## 6. Update Session Context\n\nEdit `/memories/session/stims-context.md`:\n- Root cause identified\n- Files changed\n- Test file path\n- Reproduction steps verified\n\n## 7. Commit & PR\n\n- Commit message: Sentence case (e.g., \"Fix preset loading race condition\")\n- Include: root cause in description, step to reproduce, verification in the PR\n\n---\n\n**Getting stuck?** See:\n- Runtime issues: `.agent/skills/verify-visualizer-work/SKILL.md` → Testing section\n- Visual issues: `docs/agents/visual-testing.md` → Troubleshooting\n- Architecture: `docs/ARCHITECTURE.md`", "variables": [], "notes": "Guide for diagnosing and fixing a bug end-to-end: from reproduction to test to verification. Use when addressing reported issues or regressions.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/zz-plant/stims", "path": ".github/prompts/fix-bug.prompt.md", "ref": "7c84ae22cf4a8053d23cddab5ba2cca2168d8e33", "url": "https://github.com/zz-plant/stims/blob/7c84ae22cf4a8053d23cddab5ba2cca2168d8e33/.github/prompts/fix-bug.prompt.md", "key": "zz-plant/stims/.github/prompts/fix-bug.prompt.md" } } }

fix-bug

About

Fix a Bug

1. Reproduce and Understand

2. Write a Failing Test

3. Fix the Bug

4. Verify No Regressions

5. Full Validation

6. Update Session Context

7. Commit & PR

Install fix-bug and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews