skills.rest
luispabon
luispabonCOMMUNITY
Explore all skills by this author →
GitHub

slop-detector

Crawl codebase directories to identify technical debt and code smells.

6|Updated Apr 15, 2026
Search Tags:#automation#refactoring#audit#code-quality#technical-debt#code-hygiene
One-click install
npx skills add https://github.com/luispabon/ai-bits-and-pieces --skill slop-detector-luispabon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: slop-detector
Source: https://github.com/luispabon/ai-bits-and-pieces/tree/main/skills/slop-detector
Command: npx skills add https://github.com/luispabon/ai-bits-and-pieces --skill slop-detector-luispabon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies accumulated technical debt, code smells, and complexity issues across an entire codebase, providing a structured, actionable report that allows developers to clean up messy code efficiently.

Core Features & Use Cases

  • Comprehensive Audit: Crawls entire repositories to detect complexity, dead code, and non-idiomatic patterns.
  • Actionable Reporting: Generates a YAML-based report ready for automated execution by an agent.
  • Use Case: Use this skill when you need to perform a quality sweep on a legacy project to identify high-complexity methods that need refactoring or to catch regressions in code hygiene.

Quick Start

Use the slop-detector skill to perform a deep review of the current directory.

Frequently Asked Questions about slop-detector

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

FAQPage Schema
How do I automate technical debt audits across a multi-language codebase?▼

You can automate technical debt audits by crawling codebase directories to identify complexity issues and code smells. This process generates a structured YAML report across multiple programming languages to highlight areas needing refactoring.

What is the best way to detect code smells and high-complexity methods in a legacy project?▼

The best way to detect code smells in a legacy project is performing a comprehensive repository crawl. This identifies dead code, non-idiomatic patterns, and high-complexity methods, outputting an actionable report for systematic code quality maintenance.

Can I generate structured reports for automated refactoring from a code quality sweep?▼

Yes, you can generate structured reports for automated refactoring by sweeping the codebase for hygiene regressions. The output is a YAML-based audit report designed to be executed directly by an agent for code cleanup.

Does the codebase hygiene audit require any external dependencies or components?▼

No, the codebase hygiene audit requires no external dependencies or components to operate. It independently crawls your directories to produce structured technical debt reports without needing additional environment setup.

When should I perform a code hygiene audit to catch regressions in technical debt?▼

You should perform a code hygiene audit when maintaining a legacy project or needing to catch regressions in code quality. It systematically identifies accumulated technical debt and complexity issues before they impact overall repository health.

Related Skills

Explore More Software Engineering Skills→
nexxelnnexxeln
211

repo-explorer

Clone, explore, and analyze GitHub repositories for architecture and dependencies.

Community
Intermediate
ntaksh42ntaksh42
1

code-smell-detector

Detect code smells and provide refactoring recommendations for software projects.

Community
Intermediate
atstaeffatstaeff
2

project-management

Guide Scrum project setup with CI/CD pipelines and technical debt strategies.

Community
Advanced
asynkronasynkron
32

roslynator

Analyze, fix, and format C# code in .NET solutions with Roslynator CLI.

Official
Advanced