ts-review

TypeScript type design issues that bypass tsc and ESLint include unsafe type escapes, invalid state representations, and generic inference flaws. An expert code review targets these specific footguns by analyzing type boundaries and inference logic to flag subtle type-safety problems in changed code.

Run a TypeScript type safety audit on a pull request diff by targeting the changed code against the main branch. Specify a file path, PR number, or branch diff to generate severity-labeled findings with exact file and line references without posting PR comments or reporting compiler errors.

The best way to review TypeScript generics and inference in changed code is through an expert type-safety audit that analyzes type design and inference logic. This approach identifies generic issues and boundary-safety problems beyond standard lint findings, producing structured severity-labeled findings with file and line references.

Yes, you can review a specific file path instead of the full branch diff for TypeScript issues. By providing an explicit path or PR number, the review targets that specific file, while the default behavior reviews the entire current branch diff against main, excluding generated and lock or build artifacts.

No, this TypeScript review tool does not automatically post comments to the pull request. It produces severity-labeled findings with file and line references as output for the user to review, ensuring you maintain control over what feedback is shared on the pull request.

You should use a dedicated TypeScript review because tsc and ESLint miss subtle type-design and type-safety issues like invalid state representations, unsafe assertions, and generic inference flaws. A specialized review analyzes type boundaries and footguns to catch these structural problems before merge.