Slop scan

Skill brolag/neural-claude-code/skills/slop-scan

Scan a codebase for accumulated slop, technical debt, dead code, and refactor opportunities. Default is recent changes only. Use when user says 'scan for slop', 'find tech debt', 'what needs cleanup', or before a refactor sprint. Don't use as the pre-PR gate — that is /vet (lens D).From its SKILL.md

Install

npx -y skills add brolag/neural-claude-code --skill slop-scan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, as published. Nobody here has run it

/slop-scan — Detect Technical Debt

Usage

/slop-scan              # recent changes (uncommitted + staged)
/slop-scan --commits 3  # last N commits
/slop-scan src/         # changed files in a directory
/slop-scan --full       # whole project
/slop-scan --quick      # top issues only, still recent-changes unless --full

What It Detects

Code smells: functions >50 lines, files >500 lines, nesting >3 levels
Duplication: copy-pasted blocks, repeated patterns
Dead code: unused functions, commented-out code >10 lines, unused imports
Tech debt: old TODOs, deprecated APIs, outdated deps
Anti-patterns: magic numbers, tight coupling, missing error handling
AI slop: over-abstraction, unnecessary helpers, verbose comments on obvious code

Process

Select files (default = diff mode):
- Default: git diff --name-only HEAD + git diff --cached --name-only
- --commits N: git diff --name-only HEAD~N
- --full: all files by type (exclude node_modules, .git, dist, vendor)
- If no git changes found, ask before running --full
Prioritize most-changed files (git log --format=%H -- FILE | wc -l)
Grep for patterns (TODO, FIXME, unused, deprecated)
Read top hotspot files for deeper analysis
Score and rank by impact

Output

## Slop Report: [project]

**Slop Level**: Low/Medium/High
**Files scanned**: X | **Issues**: Y

### Critical (fix now)
| Issue | Location | Effort |
|-------|----------|--------|

### Quick Wins (low effort, high impact)
- [list with estimated time]

### Deep Refactors (plan for sprint)
- [list with estimated time]

### Hotspots (most problematic files)
1. file.ts — X issues

Decision Rules

High (>30 issues): pause features, refactor sprint
Medium (10-30): weekly cleanup sessions
Low (<10): maintenance mode