implement-fix

Wiring a Fix to an existing lint rule involves creating Edit primitives for the correction, updating the Violation, and adding YAML fields like safe_fix and fix_description to classify and document the automated rewrite.

Making a shuck diagnostic fixable requires the YAML fields new_code, safe_fix, and fix_description. These fields classify the fix safety, show the corrected code, and explain the automated rewrite to the user.

To test a lint autofix against the conformance corpus, you add test cases and fixtures using the testing framework. This verifies that the Edit and Fix primitives produce the expected code rewrites and preserve snapshot parity.

You need to extend facts when the existing lint rule metadata lacks the information required to identify the correct edit spans for the Fix. Extending facts allows the diagnostic to locate and apply the automated code rewrite accurately.

Yes, the autofix workflow supports both safe and unsafe Rust lint fixes. It uses the safe_fix YAML field to classify the fix path properly and requires dedicated test coverage for each scenario to ensure rule evolution parity.

The best way to turn a linter rule into an automated code rewrite is to map the diagnostic to specific edit spans, attach an Edit and Fix primitive, and update the rule's YAML metadata and test fixtures to validate the correction.