fix-properly

Root cause analysis requires tracing data flow from creation to symptom to identify the upstream origin. This Skill enforces diagnosing the true upstream cause and applying a source-level correction, rejecting consumer-side patches like casts or silenced exceptions.

Fixing type safety errors requires source-of-truth corrections rather than consumer patches. This Skill rejects workarounds like casts and fallbacks, enforcing upstream contract corrections and checking downstream consumers for ripple effects to ensure consistent resolution.

Code refactoring breaks downstream consumers when upstream contracts change without ripple-effect validation. This Skill mandates tracing value flow from creation to symptom and verifying that the source-level fix resolves the symptom consistently for all callers.

Stopping workarounds during debugging requires enforcing traceability and prohibiting silenced exceptions. This Skill rejects consumer-side patches, requiring engineers to diagnose the location, upstream cause, and correct upstream fix before making any code changes.

This approach applies to production maintenance across codebases where errors or wrong behaviors must be fixed consistently. It enforces end-to-end validation and ripple-effect checks to ensure the upstream correction fully resolves the symptom for all callers.

You should avoid quick patches and apply source-level corrections whenever a bug risks hiding the real cause. This Skill mandates root-cause diagnosis first, prohibiting casts and special cases to ensure the fix fully resolves the symptom end-to-end.