Fix Mismatches

• ruleId: the rule that flagged the violation
• file: the file containing the violation
• line: the line number
• violationId: the violation ID (if available)

Iteration 2-3 (if needed)

Repeat steps 1-5 for any remaining violations. Stop after 3 iterations or when zero ERROR violations remain.

Fix strategies by violation type

Function name drift

// Before (wrong):  getUser(userId)
// After (fixed):   getUserById(userId)

Rename the function call to match the canonical exported name.

Missing parameters

// Before (wrong):  cancelOrder(orderId)
// After (fixed):   cancelOrder(orderId, reason)

Read the surrounding code to determine the correct value for the missing parameter. Check request bodies, user inputs, or use a sensible default.

Field name mismatch

// Before (wrong):  user.userEmail
// After (fixed):   user.email

Replace the incorrect field name with the one defined in the shared type.

Phantom imports

// Before (wrong):  import { validate } from './helpers'
// After (fixed):   import { validateInput } from './utils/validation'

Find the actual module and function name, update the import path and binding.

Important

• Always read the canonical type/function definition before applying a fix
• When adding missing parameters, use context from the surrounding code
• After applying fixes, ALWAYS revalidate to confirm
• If a fix introduces new violations, prioritize fixing those in the next iteration