Lint
A static code analysis tool that scans for style issues and common defect patterns without executing the code.
Timeline (last 90 days)
The difference between lint and testing is that tests verify "whether code behavior matches expectations," whereas lint checks, without running the code, "whether the code's writing style itself belongs to a known bad pattern."
Lint is a general term for static code analysis tools, originally used in C to detect suspicious code patterns that may cause bugs, and today mature implementations exist in most language ecosystems (such as ESLint, RuboCop, Clippy).
For Agents, the value of lint lies in its extremely fast feedback, clear rules, and machine-interpretability, requiring almost no extra explanation cost, making it very suitable as the first line of automated guardrails.
Lauren Tan reviews merged PRs by sampling spot checks rather than fully blocking review, and focuses on error patterns that Agents repeatedly make in order to fix the environment (such as adjusting lint rules, type constraints, or skills).
In Lauren Tan's metaphor, Skills correspond to recipes and operating procedures, CLI and deterministic scripts correspond to kitchen-specific tools, Lint rules and the type system correspond to physical constraints, and the verification loop corresponds to the tasting and quality-control steps.
One of the earliest static analysis tools was Lint, developed at Bell Labs in the 1970s, used to detect suspicious usage in C language code.
Lint最早由贝尔实验室的Stephen C. Johnson在1978年为C语言编写
All Facts (8)
软件工程中的验证手段从轻量到重量依次为：静态分析（Lint）、类型检查（Type Check）、单元测试、集成测试、端到端测试
95%UnverifiedFor Agents, the value of lint lies in its extremely fast feedback, clear rules, and machine-interpretability, requiring almost no extra explanation cost, making it very suitable as the first line of automated guardrails.
50%UnverifiedLint is a general term for static code analysis tools, originally used in C to detect suspicious code patterns that may cause bugs, and today mature implementations exist in most language ecosystems (such as ESLint, RuboCop, Clippy).
50%UnverifiedThe difference between lint and testing is that tests verify "whether code behavior matches expectations," whereas lint checks, without running the code, "whether the code's writing style itself belongs to a known bad pattern."
50%UnverifiedLauren Tan reviews merged PRs by sampling spot checks rather than fully blocking review, and focuses on error patterns that Agents repeatedly make in order to fix the environment (such as adjusting lint rules, type constraints, or skills).
50%UnverifiedIn Lauren Tan's metaphor, Skills correspond to recipes and operating procedures, CLI and deterministic scripts correspond to kitchen-specific tools, Lint rules and the type system correspond to physical constraints, and the verification loop corresponds to the tasting and quality-control steps.
50%UnverifiedOne of the earliest static analysis tools was Lint, developed at Bell Labs in the 1970s, used to detect suspicious usage in C language code.
50%UnverifiedLint最早由贝尔实验室的Stephen C. Johnson在1978年为C语言编写
50%