modelscope.cn

eng-ai-slop-remover

This skill should be used when the user asks to "remove AI slop", "clean up AI code", "remove AI patterns", "fix AI-generated code", "clean up PR", "remove unnecessary comments", "fix defensive checks", or mentions AI slop, AI code cleanup, or code quality issues from AI-assisted development.

Installation

$ npx skills add https://modelscope.cn

Summary

  • This skill should be used when the user asks to "remove AI slop", "clean up AI code", "remove AI patterns", "fix AI-generated code", "clean up PR", "remove unnecessary comments", "fix defensive checks", or mentions AI slop, AI code cleanup, or code quality issues from AI-assisted development.
  • Identifies and removes unnecessary comments, defensive checks, type casts to any, and style inconsistencies.

Also in this package

Other skills from modelscope.cn · top by installs.

npx skills add https://modelscope.cn

Browse all from modelscope.cn

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
LicenseMIT
More metadata
author
hungv47
version
1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,223 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

AI Slop Remover

Remove AI-generated code patterns that are inconsistent with human-written code in the codebase.

Workflow

  1. Get the diff against main branch
  2. For each changed file, analyze patterns to remove
  3. Make edits to remove identified slop
  4. 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 any that 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."