dotnet-slopwatch

Detect LLM-introduced slop in .NET code modifications.

Updated Dec 4, 2022

Search Tags:#code quality #testing #ci/cd #code review #llm #dotnet

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents Large Language Models (LLMs) from introducing "slop" into .NET codebases by masking real problems with shortcuts, ensuring code quality and test reliability.

Core Features & Use Cases

Slop Detection: Identifies common LLM shortcuts like disabled tests, warning suppressions, and empty catch blocks.
Baseline Management: Establishes a baseline to differentiate new issues from existing technical debt.
Use Case: After an LLM modifies C# source files or project configurations, run this Skill to automatically scan for and report any introduced "slop," preventing regressions and maintaining code integrity.

Quick Start

Run slopwatch to analyze the current code changes for any 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 .NET code modifications?▼

Detect LLM reward hacking by scanning C# source files, project files, and test files for patterns like disabled tests, warning suppressions, and empty catch blocks. This prevents LLM-introduced slop from masking real problems and degrading code quality.

What is code slop in C# and how does it mask technical debt?▼

Code slop in C# consists of LLM shortcuts like disabled tests, warning suppressions, and empty catch blocks that mask real problems. These shortcuts create hidden technical debt by bypassing actual error handling and suppressing necessary test failures.

How do I prevent disabled tests and empty catch blocks from LLM modifications in CI/CD?▼

Prevent disabled tests and empty catch blocks in CI/CD by integrating automated quality gates that analyze C# source files and test files. The scan identifies LLM-introduced slop and establishes a baseline to track new issues against existing technical debt.

Can I track new warning suppressions against an existing baseline in .NET?▼

Yes, you can track new warning suppressions by establishing a baseline that differentiates new issues from existing technical debt. This baseline approach ensures only LLM-introduced slop in recent code modifications is flagged during quality checks.

Does slopwatch work with C# project files and test files?▼

Yes, slopwatch analyzes C# project files and test files alongside source files. It scans these file types for LLM shortcuts such as disabled tests and warning suppressions, then reports any new issues introduced after LLM modifications.

What are the limitations of detecting LLM slop in .NET codebases?▼

Detection focuses on specific LLM slop patterns like disabled tests, warning suppressions, and empty catch blocks. It requires establishing an accurate baseline to differentiate new issues from existing technical debt, meaning pre-existing untracked issues may not be flagged.