Verification gate: lint integration #22

Open
opened 2026-04-07 20:24:09 +00:00 by austin · 0 comments
Owner

Implement lint-based verification of generated code.

  • Run the project's linter (ruff by default, configurable) on the modified file
  • Parse lint output into structured error objects (file, line, code, message)
  • Distinguish between errors (candidate fails) and warnings (pass with note)
  • Only lint the modified file, not the whole project
  • Support disabling via config for projects without a linter

Catches a class of errors that parse correctly but are still wrong: unused variables, unreachable code, import issues.

Implement lint-based verification of generated code. - Run the project's linter (ruff by default, configurable) on the modified file - Parse lint output into structured error objects (file, line, code, message) - Distinguish between errors (candidate fails) and warnings (pass with note) - Only lint the modified file, not the whole project - Support disabling via config for projects without a linter Catches a class of errors that parse correctly but are still wrong: unused variables, unreachable code, import issues.
Sign in to join this conversation.
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
austin/localcode#22
No description provided.