dotnet-slopwatch

Detect LLM reward hacking in .NET code changes with SW001–SW006 rules.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/Thorstensen/claude-template --skill dotnet-slopwatch-thorstensen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-slopwatch
Source: https://github.com/Thorstensen/claude-template/tree/main/.claude/skills/slopwatch
Command: npx skills add https://github.com/Thorstensen/claude-template --skill dotnet-slopwatch-thorstensen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects LLM reward hacking in .NET code changes and flags shortcuts that mask real problems, helping maintain code quality after every modification.

Core Features & Use Cases

  • Real-time detection of common slop patterns in C# source, project files, and tests.
  • Baseline-driven workflow to separate legacy issues from new risks, with guidance for integration into CI pipelines.
  • Optional Claude code-hook integration to automatically analyze edits during workflows.

Quick Start

Run slopwatch analyze after every LLM-generated code modification to catch and block new slop.

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?

Detect LLM reward hacking in .NET code changes by running an analysis on C# source files, project files, and tests after every modification to flag shortcuts that mask real problems.

What is slop in C# source files and project files?

Slop in C# source files and project files refers to shortcuts introduced by LLMs that mask real problems, which detection rules like SW001–SW006 identify to maintain code quality after edits.

How do I integrate slop detection into a CI pipeline for .NET projects?

Integrate slop detection into a CI pipeline by applying baseline-driven analysis to .NET project modifications, separating legacy issues from new risks using the SW001–SW006 enforcement rules.

Can I automatically analyze .NET code edits during a Claude workflow?

Yes, you can automatically analyze .NET code edits during workflows through optional Claude code-hook integration, which triggers analysis of C# source and test files after every modification.

How do I separate legacy code issues from new LLM risks in .NET projects?

Separate legacy code issues from new LLM risks in .NET projects by establishing a baseline, then enforcing the SW001–SW006 rules on subsequent code modifications to catch new slop patterns.

Do I need a baseline to detect slop in .NET code modifications?

Yes, a baseline is needed to effectively detect slop in .NET code modifications, allowing the workflow to distinguish pre-existing legacy issues from newly introduced LLM reward hacking risks.