deslop

name	deslop
description	Remove AI slop from every file in the repository while preserving behavior and genuine information.
disable-model-invocation	true

Deslop

Strip slop: content that clashes with the evidence supplied by the file, its siblings, or the repository's established conventions. This is a full-repository pass, not a diff review.

Branch References

Load the rule set that matches each file before judging it:

• Code: CODE.md
• Prose and documentation: PROSE.md
• Data and configuration: DATA.md

Apply more than one rule set when a file mixes concerns. A listed smell is a prompt to compare context, not automatic permission to delete.

Process

1. Inventory every tracked, non-generated file in scope and identify a representative sibling for each file family.
2. Read one file and its sibling completely, then load the applicable branch reference.
3. Mark only differences that lack a behavioral, informational, or local-style reason.
4. Remove the smallest proven slop. Preserve behavior, contracts, historical constraints that remain active, and intentional voice.
5. Run the narrowest relevant validation after each coherent edit group.
6. Re-read every scoped file after the pass and account for it in the final report.

Boundaries

• Do not turn stylistic preferences into universal bans. Adverbs, passive voice, comments, guards, hardcoded values, and abstraction can all be valid in context.
• Do not delete an artifact merely because static search finds no reference; use dead-code-audit when reachability is the question.
• Do not rewrite user-authored prose into a uniform voice without evidence from sibling documents.
• Do not modify generated output, vendored code, lockfiles, or binary assets unless the request includes them and their source-of-truth path is known.

Completion Criterion

The pass is complete when every scoped file is recorded as unchanged or edited, every edit has a sibling or repository-convention justification, behavioral validation passes for affected code and config, a second complete read yields no further evidence-backed slop, and the report names edited file counts plus any excluded generated or binary paths.