code_lint

code_lint runs the project’s linter and maps warnings and errors to named functions in the graph. Use it instead of running clippy, eslint, or other linters directly.

Usage

code_lint()

Output

Lint: 0 errors, 4 warnings

WARNING  UserService.findAll (src/services/user.ts:88)
  unused variable `count`

WARNING  OrderController.create (src/controllers/order.ts:51)
  Promise returned from async function is not handled

WARNING  db.query (src/db/client.ts:12)
  variable declared but never used: `timeout`

When to use

• After writing new code — catch style issues and potential bugs before committing
• As part of the build-fix-verify loop
• Replace cargo clippy, eslint, pylint — the graph mapping shows exactly which functions need attention

Workflow

code_build()   → compilation errors first
code_test()    → test failures
code_lint()    → style and static analysis warnings

Run these three in sequence after any significant change. code_lint is last because warnings do not block the build, but they should be resolved before merging.