slopwatch

Detect code smells and technical debt in .NET applications using the Slopwatch CLI.

10|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill slopwatch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slopwatch
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/slopwatch
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill slopwatch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies and helps manage "slop" – shortcuts taken by LLMs that compromise code quality and maintainability, such as disabled tests, suppressed warnings, and empty catch blocks.

Core Features & Use Cases

  • Slop Detection: Analyzes C# source files, project files, and test files for common LLM shortcuts.
  • Baseline Management: Establishes a baseline to differentiate legacy issues from new slop.
  • CI/CD Integration: Seamlessly integrates into GitHub Actions and Azure Pipelines for automated quality gates.
  • Use Case: After an LLM modifies your codebase, run Slopwatch to ensure it hasn't introduced disabled tests or warning suppressions, maintaining code integrity.

Quick Start

Run slopwatch analyze to detect code smells in the current directory.

Frequently Asked Questions about slopwatch

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

FAQPage Schema
How do I detect LLM-generated code smells in .NET applications?

To detect LLM-generated code smells in .NET applications, you can run the slopwatch analyze command to scan C# source files, project files, and test files for common shortcuts like disabled tests, suppressed warnings, and empty catch blocks.

Can I integrate code smell detection into my CI/CD pipeline?

Yes, you can integrate code smell detection into your CI/CD pipeline. Slopwatch seamlessly integrates into GitHub Actions and Azure Pipelines to act as an automated quality gate after LLM-generated code modifications.

How do I manage legacy technical debt versus new code smells in C#?

To manage legacy technical debt versus new code smells in C#, you can establish a baseline using Slopwatch. This baseline differentiates pre-existing issues from newly introduced slop, ensuring you only flag recent LLM shortcuts.

What types of shortcuts do LLMs introduce that compromise .NET code quality?

Shortcuts LLMs introduce that compromise .NET code quality include disabled tests, suppressed warnings, and empty catch blocks. These shortcuts reduce code maintainability and integrity, requiring dedicated detection to manage.

Do I need a specific CLI tool to analyze .NET code smells?

Yes, you need the Slopwatch CLI tool installed and configured to analyze .NET code smells. This CLI tool handles the analysis and baseline management required to detect LLM-generated shortcuts in your codebase.