no-workarounds

To stop using workarounds and fix root causes during debugging, enforce gate functions that detect and reject common patches like type assertions, lint suppressions, error swallowing, timing hacks, and monkey patches. This enforces disciplined root-cause analysis over symptom patching.

The best way to prevent technical debt from type assertions and lint suppressions is to apply automated detection rules that catch and reject these workaround patterns during code review or bug fixes, ensuring developers address the underlying root causes instead of masking symptoms.

Yes, you can use automated gate functions to catch error swallowing and monkey patches during code review. These checks activate during bug fixes, planning, and testing to reject workaround patterns and enforce root-cause fixes, improving overall code quality.

You need to enforce root-cause fixes instead of applying timing hacks whenever you are debugging, planning, reviewing code changes, or making architecture decisions. Replacing timing hacks with root-cause fixes reduces long-term technical debt and ensures more reliable code delivery.

To start fixing a failing issue with a root-cause fix plan, identify the failing issue in your codebase and outline a plan that addresses the underlying cause directly. Use guiding principles and references to support disciplined engineering and avoid symptom patches.