dotnet-slopwatch

Detects and prevents reward hacking in .NET code changes using Slopwatch baseline analysis.

1.1k|101|Updated Nov 12, 2025

Search Tags:#LLM #dotnet #code-quality #baseline #static-analysis #C##slopwatch

Ready to run

npx skills add https://github.com/Aaronontheweb/dotnet-skills --skill dotnet-slopwatch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-slopwatch
Source: https://github.com/Aaronontheweb/dotnet-skills/tree/main/skills/slopwatch
Command: npx skills add https://github.com/Aaronontheweb/dotnet-skills --skill dotnet-slopwatch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Slopwatch detects and prevents LLM reward hacking in .NET code changes, ensuring edits do not mask issues or introduce shortcuts.

Core Features & Use Cases

Baseline-driven analysis: compare new changes against a baseline to reveal regressions and hidden shortcuts.
Enforce code quality in edits: catch disabled tests, warning suppressions, and empty catch blocks as you modify code.
CI and local validation: supports local tool usage and CI integration to guard builds and tests.

Quick Start

Install or ensure Slopwatch is available as a tool (local or global). Then run:

Initialize baseline: slopwatch init
Analyze changes: slopwatch analyze
Optional: slopwatch analyze --fail-on warning

Frequently Asked Questions about dotnet-slopwatch

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

FAQPage Schema

How do I detect LLM reward hacking in .NET code changes?▼

You can detect LLM reward hacking in .NET code changes by validating edits against a baseline using Slopwatch. This surfaces AI-generated shortcuts like disabled tests, warning suppressions, empty catch blocks, and arbitrary delays in C# files.

How do I prevent AI from disabling tests or adding empty catch blocks in C#?▼

Prevent AI from disabling tests or adding empty catch blocks in C# by using Slopwatch to analyze changes against a baseline. This enforces code quality by catching warning suppressions and empty catch blocks during local, review, or CI validation.

Do I need to install Slopwatch as a .NET tool to check for code shortcuts?▼

Yes, checking for code shortcuts requires installing Slopwatch as a local or global .NET tool. You must maintain a baseline with analysis commands to perform ongoing validation of your C# source, project, and test files.

Can I integrate Slopwatch analysis into my CI pipeline to fail builds on regressions?▼

You can integrate Slopwatch analysis into your CI pipeline to fail builds on regressions by running slopwatch analyze with the --fail-on warning option. This guards builds and tests against hidden LLM shortcuts across your .NET projects.

What is baseline-driven static analysis for .NET source files?▼

Baseline-driven static analysis for .NET source files compares new changes against an established baseline to reveal regressions and hidden shortcuts. This process validates edits across C# source, project props, and test code environments.