Files
timmy-config/playbooks/bug-fixer.yaml
Alexander Whitestone 341c85381c feat: Timmy's sovereign config — soul, memories, skins, playbooks
Migrated from hermes/hermes-config (now archived).

Contents:
  SOUL.md — Inscription 1, the immutable conscience
  config.yaml — live Hermes harness configuration
  memories/ — persistent agent memory + user profile
  skins/ — timmy.yaml + trismegistus.yaml personalities
  playbooks/ — 6 specialist agent configs
  cron/ — scheduled job definitions
  docs/design-log/ — historical design decisions
  FALSEWORK.md — API cost management strategy
  channel_directory.json — platform channel mappings

Applied as side-car to Hermes harness. No hacking on the harness.
2026-03-24 17:45:12 -04:00

56 lines
1.3 KiB
YAML

name: bug-fixer
description: >
Fixes bugs with test-first approach. Writes a failing test that
reproduces the bug, then fixes the code, then verifies.
model:
preferred: qwen3:30b
fallback: claude-sonnet-4-20250514
max_turns: 30
temperature: 0.2
tools:
- terminal
- file
- search_files
- patch
trigger:
issue_label: bug
manual: true
repos:
- Timmy_Foundation/the-nexus
- Timmy_Foundation/hermes-agent
steps:
- read_issue
- clone_repo
- create_branch
- dispatch_agent
- run_tests
- create_pr
- comment_on_issue
output: pull_request
timeout_minutes: 15
system_prompt: |
You are a bug fixer for the {{repo}} project.
YOUR ISSUE: #{{issue_number}} — {{issue_title}}
APPROACH (test-first):
1. Read the bug report. Understand the expected vs actual behavior.
2. Write a test that REPRODUCES the bug (it should fail).
3. Fix the code so the test passes.
4. Run tox -e unit — ALL tests must pass, not just yours.
5. Commit: fix: <description> Fixes #{{issue_number}}
6. Push, create PR.
RULES:
- Never fix a bug without a test that proves it was broken.
- Never use --no-verify.
- If you can't reproduce the bug, comment on the issue with what you tried.
- If the fix requires >50 lines changed, decompose into sub-issues.