slop-hunter-ts

Audit TypeScript codebases for AI-generated noise and style drift.

5|Updated Jan 14, 2026

Search Tags:#typescript #audit #code-quality #dead-code #style-drift #redundant-comments

Ready to run

npx skills add https://github.com/skyosev/agent-skills --skill slop-hunter-ts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: slop-hunter-ts
Source: https://github.com/skyosev/agent-skills/tree/main/hunter-party-ts/slop-hunter-ts
Command: npx skills add https://github.com/skyosev/agent-skills --skill slop-hunter-ts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces AI-generated noise in TypeScript code by removing redundant comments, verbose documentation, and dead code, helping codebases stay readable and maintainable.

Core Features & Use Cases

Detect redundant comments that narrate obvious behavior.
Flag verbose or redundant JSDoc and documentation that restates code.
Identify style drift from project conventions and naming.
Surface trivially dead code and unused imports.
Use during code reviews, pre-merge checks, or branch hygiene passes.

Quick Start

Audit a TS codebase to surface AI-generated noise and drift, producing a prioritized list of actionable changes.

Frequently Asked Questions about slop-hunter-ts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect and remove AI-generated noise in TypeScript code?▼

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.

What is the best way to find redundant comments and dead code in a TS codebase?▼

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.

Can I use a TypeScript code audit on branch diffs for pre-merge checks?▼

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.

How does an AI code audit identify style drift in TypeScript files?▼

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.

Do I need to configure project conventions before auditing for style drift?▼

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.