Deslop

Remove AI-style code slop from a branch by reviewing diffs, deleting inconsistent defensive noise, and preserving behavior and local style.

Security Scan

The skill's instructions match its stated purpose (clean code diffs), but there are internal inconsistencies—most notably undeclared required tooling and vague edit/commit behavior—so proceed with caution and set operational safeguards.

Purpose & Capability

The name, description, heuristics document, and workflow all align: this skill is intended to scan branch diffs and remove AI-style 'slop' while preserving behavior and style. There are no requested credentials or unrelated capabilities in metadata.

Instruction Scope

SKILL.md instructs the agent to run git diff, use ripgrep (rg) to build candidate lists, and run project checks (bun check, bun typecheck), then edit files and 'fix regressions'. These actions are within the stated purpose (review and edit code), but the instructions are somewhat open-ended about committing changes, authorizing edits, and what counts as an acceptable fix. The guardrails are sensible but rely heavily on subjective judgment, so human review and explicit commit/PR policies are recommended.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That minimizes installation risk.

Credentials

The skill declares no required environment variables or credentials (appropriate), but SKILL.md expects tools that are not declared as required: git, rg (ripgrep), and bun. This mismatch is noteworthy because the agent may assume those tools are available or attempt to run them; lack of explicit declared binaries is an operational/integrity gap rather than a secret-exfiltration risk.

Persistence & Privilege

always is false and there is no install or configuration of persistent privileges. The skill does instruct modifying repo files, but it does not request system-level persistence or modify other skills/configurations.

Scan Findings in Context

[regex-scanner-empty] expected: The static regex scanner had no code files to analyze (this is instruction-only). This is expected for a purely documentation/instruction skill; absence of findings is not evidence of safety.

What to consider before installing

This skill appears to be what it claims (clean up generated-code 'slop'), but it has a few practical gaps you should address before allowing it to run with write access to a repo: 1) Ensure the runtime has the tools SKILL.md assumes (git, rg, bun) or update the skill to declare them. 2) Decide an explicit workflow for code edits: run in a sandboxed branch, require human review or PRs, and keep backups so changes are reversible. 3) Require CI/tests to run on any changes (the skill suggests running typechecks but behavior for commits is undefined). 4) Because the agent will run shell commands and edit files, restrict autonomous invocation or require explicit user confirmation before applying edits. If you want to use this skill, ask the publisher to add declared required binaries and clarify commit/PR/approval behavior; otherwise run it only in a controlled environment where you can review its edits.

When to use this skill

Use when asked to:

• "remove AI slop"
• "clean up generated code style"
• "review branch diff for weird comments/defensive checks/casts"

Workflow

1. Set comparison base (default main) and inspect git diff <base>...HEAD.
2. Build a candidate list using rg over added lines (comments, catches, casts, lint ignores, placeholders, debug leftovers).
3. Review each candidate in full file context and compare with nearby local patterns.
4. Remove only inconsistent slop; keep behavior and domain-valid guards.
5. Re-run project checks (bun check, bun typecheck) and fix regressions.
6. Report exact files changed and what slop was removed vs intentionally kept.

Slop checklist

Read and apply: references/slop-heuristics.md

Guardrails

• Do not remove protections at trust boundaries (user input, auth, network, db, file I/O).
• Do not replace real typing with weaker typing.
• Prefer minimal edits over broad rewrites.
• Keep project conventions (hooks/query style, component patterns, naming).