slopwatch

Detect code smells and technical debt in .NET C# applications.

71|10|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/wshaddix/dotnet-skills --skill slopwatch-wshaddix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slopwatch
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/slopwatch
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill slopwatch-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers identify and prevent "slop" – shortcuts taken by LLMs (or humans) that lead to code quality issues, masked bugs, and technical debt.

Core Features & Use Cases

  • Automated Code Smel Detection: Identifies disabled tests, warning suppressions, empty catch blocks, and other common shortcuts.
  • CI/CD Integration: Can be integrated into pipelines to fail builds if new slop is introduced.
  • Use Case: After an LLM modifies C# code, run Slopwatch to ensure it hasn't introduced disabled tests or suppressed critical warnings, maintaining code integrity.

Quick Start

Run slopwatch analyze to check the current directory for code smells.

Frequently Asked Questions about slopwatch

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

FAQPage Schema
How do I detect LLM reward hacking in C# code?

Detect LLM reward hacking in C# code by scanning source, project, and test files to identify shortcuts like disabled tests, suppressed warnings, empty catch blocks, and arbitrary delays that mask bugs and introduce technical debt.

What are common code smells in .NET applications caused by AI coding assistants?

Common code smells in .NET applications caused by AI coding assistants include disabled tests, warning suppressions, empty catch blocks, and arbitrary delays, which introduce hidden technical debt and degrade overall code quality.

Can I integrate code smell detection into CI/CD pipelines for .NET projects?

Yes, you can integrate code smell detection into CI/CD pipelines for .NET projects to automatically fail builds when new technical debt or shortcuts like disabled tests and suppressed warnings are introduced by automated coding tools.

How do I validate C# source files for technical debt after an LLM modifies code?

Validate C# source files for technical debt after an LLM modifies code by running an analysis command to check the directory for introduced code smells, ensuring code integrity by catching disabled tests or suppressed critical warnings.

Does code smell detection work with both project files and test files in .NET?

Yes, code smell detection works with both project files and test files in .NET. It analyzes these files to find patterns like disabled tests and suppressed warnings, ensuring comprehensive quality validation across the codebase.