Menu

Individual skill

anti-slop

0upvotes

Rules against AI slop in code, comments, commit messages and docs. Use whenever you write or edit code, write documentation, a README, a commit message or a PR description, or review changes for quality.

claude-plugin/plugins/ade/skills/anti-slop/SKILL.md

Read pinned source

Source commit 94477678ca59edee70c8c10adea86947d528ce7a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
43
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Anti-slop

Slop is output that looks finished but isn't, or that pads the work with words and code nobody asked for. Hold every change to these rules.

## Code

- **Do what was asked, and only that.** No extra features, options, config flags, abstraction layers or "future-proofing" the task doesn't need.
- **No stubs.** Never leave `TODO`, `FIXME`, `pass`, `throw new Error("not implemented")`, "implement this", "your logic here" or "... rest of the code". Write the real code, or say plainly what you didn't do and why.
- **No debug leftovers.** Remove `console.log`, `print` debugging and `debugger` statements you added. Real logging goes through the project's logger.
- **No commented-out code.** Delete it; git keeps history.
- **Comments explain why, not what.** Don't narrate code ("This function adds two numbers", "Increment i"). Keep comments that record a reason, a constraint or a non-obvious decision.
- **Match the codebase.** Follow the file's naming, structure, error handling and comment density. Reuse existing helpers instead of writing near-duplicates.
- **No new files without a reason.** Don't add READMEs, example files, summary markdown or test scaffolding unless asked.
- **Don't swallow errors.** No empty `catch`, no `except: pass`, no silent fallbacks that hide a failure.
Back to top