Dotnet Slopwatch

This is a .NET linter that catches the shortcuts LLMs take to make tests pass without fixing the actual problem. It detects disabled tests, suppressed warnings, empty catch blocks, arbitrary delays, and project-level warning suppressions. You run it after every code change, ideally as a post-edit hook, and it compares against a baseline so you're only catching new slop rather than inherited tech debt. The strict mode treats everything as an error, which is the right call when working with AI coding assistants that will happily disable a flaky test instead of fixing the race condition. It's opinionated tooling for a real problem: reward hacking in generated code.

skills.sh installs: 580
GitHub stars: 1.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aaronontheweb/dotnet-skills --skill dotnet-slopwatch --agent claude-code

Installs into .claude/skills of the current project.

Files

Slopwatch: LLM Anti-Cheat for .NET

When to Use This Skill

Use this skill constantly. Every time an LLM (including Claude) makes changes to:

C# source files (.cs)
Project files (.csproj)
Props files (Directory.Build.props, Directory.Packages.props)
Test files

Run slopwatch to validate the changes don't introduce "slop."

What is Slop?

"Slop" refers to shortcuts LLMs take that make tests pass or builds succeed without actually solving the underlying problem. These are reward hacking behaviors - the LLM optimizes for apparent success rather than real fixes.