slop-hunter-ts

To remove AI-generated noise in TypeScript code, audit your codebase to detect redundant comments, verbose JSDoc, style drift, and trivially dead code. The audit classifies findings by project conventions and produces a structured report citing exact file paths and lines for actionable changes.

The best way to find redundant comments and dead code is running an audit that identifies AI-generated noise and style drift. It surfaces trivially dead code, unused imports, and comments narrating obvious behavior, outputting a prioritized list of actionable changes for code reviews.

Yes, you can audit TypeScript code during pre-merge checks by applying it across branch diffs or full path scopes. This focuses specifically on added noise in TS files to help maintain codebase readability and hygiene before merging.

An AI code audit identifies style drift in TypeScript files by comparing code against established project conventions and naming patterns. It flags deviations and verbose documentation that restates code, classifying findings into a structured report for branch hygiene passes.

Configuring project conventions before auditing for style drift is essential because the audit classifies findings based on those conventions. Defining naming patterns and documentation standards ensures the structured report accurately flags deviations, verbose documentation, and redundant comments.