slop-code
From the author
Slop review and repair for source code, tests, configuration, generated documentation, README files, commit messages and pull request descriptions. Use when someone asks to review generated or agent-written code for quality, asks whether a diff is padded or ceremonial, asks about hallucinated or slopsquatted imports, or asks to clean up comments, docstrings, wrapper functions, defensive try/except blocks, or tests that assert nothing. Runs the load-bearing test: delete the comment, wrapper, handler or assertion-free test and name what broke. Runs the package existence scanner over every import. Reviews commit and pull request text for canned policy assurances and preserved-information boilerplate. Reports defects with severity and confidence separated, never an authorship verdict, and never a claim that a diff was machine written.
Install
npx skills add AgriciDaniel/anti-slop --skill slop-code -a claude-code
Installs to .claude/skills/slop-code/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 80
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- slop-reviewAgriciDaniel/anti-slopRead-only slop review of prose, documentation, reports, agent output, commit messages or PR descriptions. Use when someone asks what is wrong with a draft, asks for an editorial or quality review, asks whether text is padded, vague, puffed up, unsourced or hollow, or asks whether writing "sounds like AI". Produces a fixed findings report where every finding carries a verbatim quote, a severity (HIGH for a fabricated fact, citation or API, MEDIUM for padding or filler that changes nothing if cut, LOW for stylistic tells) and a separate confidence (low, medium, high), plus the artifact from the structural test that produced it. This skill diagnoses only. It cannot write or edit files, it never rewrites the text it is judging, and it never states or implies who or what wrote the text. Hand its findings to slop-rewrite when the user wants repair.Engineering★ 64
- slop-rewriteAgriciDaniel/anti-slopRepair pass that consumes an existing slop-review findings report and fixes only what it lists. Use when someone asks to clean up, de-slop, tighten, fix or rewrite a draft, documentation page, report or agent output after a review has been produced, or asks to strip vendor residue and placeholder text. Cuts padding that failed the deletion test, replaces vacuous claims that failed the inversion test, resolves or removes vague attributions, and deletes vendor residue. It never invents a fact, name, number, date, quote or citation that is not already in the source. It never re-derives findings and never expands scope beyond the report. The deterministic scanners re-run after every fix and their exit codes, not the model's judgment, decide whether the pass is finished. It never states or implies who or what wrote the original.Testing★ 64
- review-codetobihagemann/turboReview code for bugs, security vulnerabilities, API misuse, consistency issues, simplicity problems, or test coverage gaps and low-value tests by running internal reviews and a peer review in parallel and returning combined findings. Single-concern with a type argument, or full review with no argument. Use when the user asks to "review my code", "full code review", "review my changes", "check for bugs", "scan for bugs", "review correctness", "security audit", "find vulnerabilities", "review security", "check API usage", "verify against docs", "check for cross-file duplication", "review consistency", "check for code reuse", "review simplicity", "find untested code", "find redundant tests", or "review test coverage".Engineering★ 416
- anti-slopalvin-reyes/better-agentic-ideRules 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.Writing★ 85
- desloprohitg00/pro-workflowRemove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, strips defensive code, and in skill-file mode lints SKILL.md files for quality. Use when cleaning up code, simplifying, removing boilerplate, before committing, or when reviewing a skill before promoting it.Engineering★ 2.9K
- secure-code-reviewnahid-sparktales/agent-dispatcherReview a change or a codebase for security defects with a deliberate reading order — where bugs cluster, trace source to sink, confirm reachability, and write a finding someone can actually fix. Use when asked to security-review a pull request, feature or repository, or before shipping anything touching auth, money, tenancy, uploads or secrets. Not a scanner run (its output is leads), not design-stage threat modeling, and not a penetration test — nothing here authorizes touching a running system.Engineering★ 59
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in