agents-orchestrator/agent-orchestrator
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
agent-orchestrator/.claude/rules/18-preexisting-issues.md
DexterFromLab 3672e92b7e feat: Agent Orchestrator — multi-project agent dashboard 
Tauri + Svelte 5 + Rust application for orchestrating multiple AI coding agents.
Includes Claude, Aider, Codex, and Ollama provider support, multi-agent
communication (btmsg/bttask), session anchors, plugin sandbox, FTS5 search,
Landlock sandboxing, and 507 vitest + 110 cargo tests.
2026-03-15 15:45:27 +01:00

962 B
Raw Blame History

Preexisting Issues

Never ignore problems you encounter in the codebase, even if they are outside the current task scope.

Rules

  • When you encounter a bug, lint error, type error, broken test, or code smell while working on a task, do not skip it.
  • If the fix is straightforward (under ~15 minutes of work), fix it in a separate commit with a clear message explaining what was wrong.
  • If the fix is complex (large refactor, architectural change, risk of regression), stop and inform the user: describe the issue, its severity, where it lives, and propose a plan to fix it. Do not attempt complex fixes without approval.
  • Never suppress warnings, disable lint rules, or add // @ts-ignore to hide preexisting issues. Surface them.
  • When fixing a preexisting issue, add a test that would have caught it if one does not already exist.
  • Track issues you cannot fix immediately: flag them to the user and, if Memora is available, create an issue memory.