Lint

You might say

Use lint to flag unused variables and unhandled promises first, but do not say a passing lint means the button really works.

Lint is static checking that uses source rules to find suspicious patterns and consistency problems without running the full program.Lint can locate unused variables, clear mistakes, or unhandled promises and make the warning disappear after a correction. It finds source-level risks early. Clicking a button and confirming save results or API responses still need build, tests, or manual verification.

Know first

JavaScript

LintLinter

How source code is scanned by rules and gets a located issue

checkout.jsScanning

11 async function submit(order) {
12   const total = price + tax;
13   await saveOrder(order)
14   return total;
15 }

Lint locates suspicious source at a file and line without running the full site.

What lint can find early

It checks source shapes and conventions: Rules find unused variables, risky patterns, or team-inconsistent code without starting the full application. Results point to a file and line for quick pre-commit correction.

Static passing is not correct running: Lint does not click buttons, wait for networks, or confirm database writes. Put it in CI as an early check, then use tests and acceptance for actual behavior.

Quick checkChoose the best answer

A PR’s lint passes, but clicking save shows no feedback. What is the most accurate judgment?

Source rules found no issue; operate or test the save flow and feedback nextPassing lint means saving is fully acceptedSince errors can still happen, do not run lint

You can say this to an AI Agent

Enable and fix lint reports for unused variables and unhandled promises. Put lint in PR checks, but still test the save button afterward: click, wait, success feedback, and failure feedback all need confirmation.

Learn next

1CI→2Unit Test→