libreqos-anti-slop

name	libreqos-anti-slop
description	Anti-slop workflow for LibreQoS. Use when changing code, docs, UI, or user-facing text. Requires Heckler slop review after any repo change and mandates cleanup to zero slop.

LibreQoS Anti-Slop Workflow

Use this skill when writing or reviewing code, docs, UI, or any user-facing text in this repo.

The goal is zero slop.

Required Workflow

1. Make your change.
2. Before returning to the user (whenever the repo has changed), invoke the heckler subagent on the current diff.
3. If heckler reports a non-zero slop score, you MUST:
   • print exactly: SLOP! SLOP! SLOP ALERT!
   • fix the slop (delete dead code, remove placeholders, rename generic identifiers, remove filler text, simplify algorithms, etc.)
   • re-run heckler until the slop score is 0/10, or explicitly explain why a residual item cannot be fixed in this scope.

This repo also uses reaper to enforce DRY/duplication and dead-code avoidance for source-code batches; see $libreqos-review-subagents-workflow.

Code Slop (Rust-first)

High-confidence slop in Rust

• todo!(), unimplemented!(), commented-out code, placeholder stubs
• unused code or #[allow(dead_code)] without a strong reason
• duplicated helpers or copy/paste logic that should reuse an existing helper/module
• generic names that hide meaning (data, result, temp, value, thing, info)
• "design pattern" scaffolding that adds layers without need