engineer-code-review

To conduct a comprehensive code review, you can use a static analysis tool that evaluates code for security vulnerabilities, performance bottlenecks, and maintainability concerns. It categorizes findings into severity levels like blocker, major, and minor to ensure high quality.

Static analysis for code quality assurance automatically examines source code without running it to identify security and performance issues. It classifies findings into structured severity levels: blocker, major, minor, nit, and praise, providing a clear report for developers.

Yes, you need ESLint and TypeScript configured in your project to perform this static code analysis. The tool requires the @typescript-eslint/parser and related ESLint plugins to accurately analyze your codebase and identify maintainability or security issues.

To generate a structured report from a TypeScript codebase review, run the analysis tool against your project directory. It evaluates the code and outputs a categorized report with findings classified by severity levels such as blocker, major, minor, nit, and praise.

No, you cannot use this code analysis tool for projects that do not use TypeScript. The static analysis explicitly requires TypeScript, ESLint, and the @typescript-eslint/parser to function correctly and identify codebase issues.