code-deslop

Removes AI-generated code residue and non-domain identifier names from branch diffs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agent coding passes leave behind slop: tautological comments, abnormal defensive checks, type escape hatches, debug chatter, and durable identifiers named after delivery stages, plan indices, or governance IDs instead of domain behavior. This Skill cleans that residue from the current branch diff while protecting security guards, fail-closed validation, and git history. ## Core Features & Use Cases - Branch-scoped cleanup: Inspects only changes introduced on the current branch versus its merge base, removing comments, scratchpad leakage, shadow helpers, silent failure fallbacks, and style drift with behavior-preserving minimal diffs. - Mandatory Naming Audit: Flags identifier residue across five pattern families (stage segments, plan/review indices, governance taxonomy as identity, ceremony tokens, synonym cycles) on task runners, artifact paths, CLI, symbols, and tests, then renames to domain-first names with a full cascade checklist. - Hard safety guards: Never invokes git-cg, git commit, amend, rebase, or history mutation; preserves SOP matrices, pin locks, redaction paths, and security-relevant checks. Commit-message draft deslop runs only on explicit user opt-in. - Use Case: After an agent implements a feature touching justfile recipes, Python modules, and tests, run a deslop pass to rename eval-s7-proof to eval-package-coverage, strip <thinking> tags and debug prints, and emit a Naming Audit table before opening the PR. ## Quick Start Ask the agent to run code-deslop on the current branch diff to remove AI code residue and audit identifier names before committing.

Frequently Asked Questions about code-deslop

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

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

Run a code-deslop pass scoped to the branch diff versus its merge base. It strips tautological comments, scratchpad tags, debug chatter, abnormal defensive checks, and type escape hatches while keeping security guards and fail-closed validation intact.

What is a naming audit for AI-written code?

A naming audit scans branch-touched identifiers for residue families: stage segments like s7, plan indices like finding_6, governance IDs like D31 or E07 used as API names, ceremony tokens like wip, and synonym cycles. Flagged names are renamed to domain-first forms.

Does code-deslop change git history or commit messages?

No. It never runs git commit, amend, rebase, or git-cg, and never mutates history. Commit-message draft cleanup happens only when the user explicitly opts in with a proposed draft, and even then no git commands are executed.

When should I not use code-deslop?

Do not use it for README, ADR, or blog prose cleanup, which belongs to a prose-deslop skill. It is also not a substitute for code review, tests, or architecture decisions, and it must not remove intentional security or schema strictness checks.

Can existing legacy names justify new similar names?

No. The anti-precedent rule forbids minting new identity names that rhyme with existing residue, such as adding S7_Rename.py because S7_tests.py exists. New branch-touched identifiers must always be domain-first.