dotnet-slopwatch

To detect LLM reward hacking in .NET code changes, analyze your code diffs for slop patterns like disabled tests, empty catch blocks, and warning suppressions using a dedicated scanning tool during code reviews or LLM sessions.

Common slop patterns in C# include disabled tests, warning suppressions, arbitrary delays, empty catch blocks, project-level suppressions, and Central Package Management bypass, all of which create silent test failures and misleading builds.

Yes, you can integrate slop detection into your CI pipeline for C# projects by running an analyzer that supports hook integration and evaluates code diffs against a configured baseline to block newly introduced reward hacking patterns.

You can enforce strict quality rules during LLM coding sessions by enabling a strict mode that elevates all slop detection rules to errors, providing rapid feedback and preventing silent test failures in .NET code.

To analyze only new code changes instead of the entire .NET repository, configure a baseline support mechanism that focuses the slop pattern diff analysis strictly on newly introduced modifications in your C# source, project, and test files.