dexter/BTerminal
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
BTerminal/.claude/rules/18-preexisting-issues.md
Hibryda ee198a2fdb chore: reorganize rules files — consolidate duplicates 
Migrates legacy rule numbering (18, 20) to standardized sequence (53, 54) and adds new 18-preexisting-issues.md for handling pre-existing issues during development. This consolidates duplicate rule coverage across the old and new numbering schemes.

Files changed:
- Removed: 18-relative-units.md (moved to 53-relative-units.md)
- Removed: 20-testing-gate.md (moved to 54-testing-gate.md)
- Added: 18-preexisting-issues.md (new)
- Added: 53-relative-units.md (renamed from 18)
- Added: 54-testing-gate.md (renamed from 20)
2026-03-12 06:47:47 +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.