eng-ai-slop-remover
AI Slop Remover
Remove AI-generated code patterns that are inconsistent with human-written code in the codebase.
Workflow
- Get the diff against main branch
- For each changed file, analyze patterns to remove
- Make edits to remove identified slop
- Report a 1-3 sentence summary of changes
Step 1: Get the Diff
git diff main --name-only
Then view each changed file to understand existing code style.
Step 2: Identify AI Slop Patterns
Comments to remove:
- Obvious or redundant comments explaining what code clearly does
- Comments that don't match the commenting style elsewhere in the file
- Section divider comments when not used elsewhere
Defensive code to remove:
- Try/catch blocks around code that doesn't throw or is already in a trusted path
- Null/undefined checks when callers guarantee valid input
- Type guards that duplicate earlier validation
- Redundant error handling when parent functions already handle it
Type issues to fix:
- Casts to
anythat bypass TypeScript's type system - Type assertions that hide real type mismatches
- Overly broad generic types when specific types exist
Style inconsistencies:
- Naming conventions that differ from the file
- Spacing/formatting patterns that differ from the file
- Import organization that differs from the file
Step 3: Make Edits
Remove identified patterns while preserving code functionality. Match the existing file's style.
Step 4: Report
End with only a 1-3 sentence summary of what was changed. No lists, no detailed breakdowns.
Example: "Removed 12 redundant comments and 3 unnecessary try/catch blocks across 4 files. Fixed 2 casts to any by using proper interface types."
More from hungv47/agent-skills
mkt-copywriting
This skill should be used when the user asks to "write copy", "create a headline", "write a tagline", "improve my copy", "write landing page copy", "create ad copy", "write email subject lines", "write product description", or mentions copywriting, persuasive writing, marketing copy, or conversion copy. Uses Harry Dry's Marketing Examples framework.
19tool-plan-interviewer
This skill should be used when the agent enters plan mode, when the user mentions "plan file", "spec file", "interview me about the plan", "help me think through this", or when starting implementation planning. Conducts in-depth, multi-round interviews using AskUserQuestion to surface non-obvious requirements, edge cases, and tradeoffs before writing specifications.
14design-user-flow
This skill should be used when the user asks to "create a user flow", "map navigation", "design user journey", "create wireflow", "plan screen transitions", "map the app flow", "design navigation", or mentions user flow, wireflow, navigation map, user journey, screen transitions, or pre-interface design research. Creates user flow diagrams and wireflows for digital products.
14eng-system-architecture
This skill should be used when the user asks to "design system architecture", "plan the tech stack", "create database schema", "design API structure", "architect the system", "plan the backend", "design infrastructure", or mentions system architecture, technical architecture, database design, API design, or tech stack selection. Transforms product documentation into comprehensive technical blueprints.
13mkt-diagnosis
This skill should be used when the user asks to "diagnose the problem", "break down the issue", "build a logic tree", "what's causing this", or mentions problem diagnosis, logic trees, MECE decomposition, or structured problem solving. This is the ENTRY POINT for problem analysis — use when no diagnosis exists yet.
13mkt-lp-optimization
This skill should be used when the user asks to "optimize a landing page", "improve conversion rates", "review my landing page", "create a high-converting landing page", "audit my LP", "reduce bounce rate", or mentions landing page design, conversion optimization, A/B testing strategy, or CTA optimization.
13