dotnet-slopwatch

Detect LLM reward hacking patterns in .NET code changes.

57|7|Updated Aug 6, 2025
One-click install
npx skills add https://github.com/seiggy/lucia-dotnet --skill dotnet-slopwatch-seiggy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-slopwatch
Source: https://github.com/seiggy/lucia-dotnet/tree/main/.github/skills/slopwatch
Command: npx skills add https://github.com/seiggy/lucia-dotnet --skill dotnet-slopwatch-seiggy

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents LLMs from introducing "slop" into your .NET codebase, ensuring code quality and preventing the masking of underlying issues.

Core Features & Use Cases

  • Detects Reward Hacking: Identifies shortcuts LLMs take to make tests pass or builds succeed without genuine fixes.
  • Common Slop Patterns: Catches disabled tests, warning suppressions, empty catch blocks, arbitrary delays, and project-level suppressions.
  • Use Case: After an LLM modifies your C# code, run this skill to automatically scan for any new instances of disabled tests or suppressed warnings before merging the changes.

Quick Start

Run slopwatch analyze after any LLM-generated code modification to detect new issues.

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 C# code changes?

Detect LLM reward hacking by scanning .NET source, project, and test files for slop patterns like disabled tests, warning suppressions, and empty catch blocks. This identifies shortcuts LLMs take to force builds to succeed without genuine fixes.

What is LLM slop in .NET codebases?

LLM slop in .NET codebases refers to low-quality code patterns introduced by AI, such as disabled tests, arbitrary delays, and project-level warning suppressions. These patterns mask underlying issues to make tests pass or builds succeed artificially.

How do I scan for disabled tests and suppressed warnings after an AI code generation?

Scan for disabled tests and suppressed warnings by running an automated analysis tool on your modified C# files. The process flags newly introduced instances of empty catch blocks and project-level suppressions to prevent masking build failures.

Can I integrate automated code quality checks into CI/CD pipelines for .NET projects?

Yes, you can integrate automated code quality checks into CI/CD pipelines for .NET projects. The analysis hooks into your pipeline to automatically scan C# source and test files for slop patterns before merging LLM-generated changes.

Does this slop detection tool work with Claude code hooks?

Yes, this slop detection tool works with Claude code hooks. It integrates directly to automatically analyze generated C# code changes for reward hacking patterns like arbitrary delays and empty catch blocks before execution.