slop-scan

Identify code smells, dead code, and technical debt across repositories.

11|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/brolag/neural-claude-code --skill slop-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slop-scan
Source: https://github.com/brolag/neural-claude-code/tree/main/skills/slop-scan
Command: npx skills add https://github.com/brolag/neural-claude-code --skill slop-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Slop Scan identifies and exposes code smells, dead code, and technical debt to prevent accumulation and enable targeted refactors.

Core Features & Use Cases

  • Inventory and analyze the repository to surface hotspots and debt.
  • Prioritize refactors with a Quick Wins view and severity scoring.
  • Generate actionable reports that guide engineers and team leads.

Quick Start

Run the slop-scan to generate a comprehensive slop report for your project.

Frequently Asked Questions about slop-scan

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

FAQPage Schema
How do I identify technical debt and dead code across an entire repository?

To identify technical debt and dead code across an entire repository, you can run a static analysis scan. This process inventories your project to surface hotspots, applies severity scoring, and generates an actionable report for targeted refactoring.

What is the best way to prioritize code refactors in a large project?

Prioritizing code refactors in a large project is best achieved by generating a Quick Wins view. This analysis scores the severity of detected code smells and technical debt, guiding engineers toward high-impact areas and recently changed directories first.

Does static analysis for code smells work on multi-language projects?

Static analysis for code smells does work on multi-language projects. The scanning process is designed to handle multiple languages within your repository, allowing you to target entire projects or specific directories to detect patterns and inventory technical debt.

How do I detect code smells and prevent code slop accumulation?

Detecting code smells to prevent code slop accumulation requires scanning your repository to expose technical debt. This analysis identifies problematic patterns, dead code, and hotspots, generating actionable reports that enable targeted refactors before debt builds up.

Can I run a code quality scan on specific targeted directories instead of the whole project?

You can run a code quality scan on specific targeted directories instead of the whole project. The analysis prioritizes changed areas and allows directory-level scanning, ensuring your technical debt reports focus precisely on active development zones.