deslop-gate

Routes deslop requests to code or prose cleanup skills while enforcing naming audits and git safety policies.

2|Updated Jun 7, 2026
One-click install
npx skills add https://github.com/Thomo1318/gitCommitGenerator --skill deslop-gate-thomo1318
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deslop-gate
Source: https://github.com/Thomo1318/gitCommitGenerator/tree/main/.agents/skills/deslop-gate
Command: npx skills add https://github.com/Thomo1318/gitCommitGenerator --skill deslop-gate-thomo1318

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated code and prose often accumulate "slop": stage-indexed file names, finding-numbered symbols, governance IDs used as identifiers, filler prose, and ceremony comments. Without a gate, cleanup passes can also accidentally mutate git history, amend commits, or clobber SOP-governed commit conventions. This Skill provides a single entrypoint that classifies deslop requests, refuses unsafe surfaces, and dispatches to the correct domain skill. ## Core Features & Use Cases - Request classification and routing: Directs code slop to code-deslop, prose slop to prose-deslop, and pasted commit-message drafts to a bounded text-only cleanup path. - Hard refusal policy: Blocks git mutations (commit, amend, rebase, git-cg), SOP/gitmoji authority changes, and secret-file edits, keeping commit authority with the user. - Mandatory Naming Audit: Requires pattern-based detection of residue families A–E (stage/slice indices, plan/review indices, governance taxonomy as identity, ceremony names, synonym cycles) on durable surfaces like recipes, paths, CLI, and symbols. - Use Case: A user pastes a draft commit message and asks to "deslop it" — the gate allows text-only cleanup with no git side effects, while a request to "amend HEAD" is refused with a one-paragraph reason. ## Quick Start Ask the assistant to deslop the current branch diff and require a Naming Audit of recipe and symbol names before finishing.

Frequently Asked Questions about deslop-gate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove AI-generated slop from code safely?

Invoke the deslop gate with a code target such as a branch diff, tests, or just recipes. It routes to the code-deslop skill, which renames stage-indexed and finding-indexed identifiers to domain-first names and runs lint plus a naming scan to verify no residue remains.

Can deslop cleanup rewrite or amend git commit history?

No. The gate refuses all git mutations including commit, amend, rebase, and git-cg invocation. The only exception is text-only cleanup of a pasted draft commit message, which never touches the repository or git state.

What is a Naming Audit in a deslop workflow?

A Naming Audit scans durable surfaces like recipes, paths, CLI, and symbols for residue pattern families A–E, including stage indices, finding numbers, and governance IDs used as identity. Citations in matrices and ADRs are preserved while identity names are renamed.

When should I use code-deslop versus prose-deslop?

Use code-deslop for source, tests, scripts, and recipe naming; use prose-deslop for docs, ADRs, PR bodies, and README text. If both are requested, they run sequentially with code first and one shared Naming Audit at the end.

Why does the deslop naming scan exit with code 2?

Exit code 2 means identity residue matching families A–D remains on durable surfaces after the cleanup pass. You must finish the renames and cascade changes before the gate can report the deslop as complete.