slop-rewrite
De la autor
Repair 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.
Instalare
npx skills add AgriciDaniel/anti-slop --skill slop-rewrite -a claude-code
Se instalează în .claude/skills/slop-rewrite/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 80
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- slop-codeAgriciDaniel/anti-slopSlop 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.Inginerie★ 64
- 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.Inginerie★ 64
- slop-verifyAgriciDaniel/anti-slopVerification pass for citations, links, package names and vendor residue. Use when someone asks whether the sources in a document are real, asks to check DOIs, ISBNs, arXiv IDs or URLs, asks whether a cited source actually supports the claim attached to it, asks to check that imported packages exist, or asks to strip vendor artifacts such as oaicite, cite spans, lenticular bracket citations, grok cards or utm_source tracking parameters. This is the only layer allowed to hard-fail, because existence and resolution are decidable. It runs the attribution test on every vague authority claim and resolves it to a named source or reports it unresolved. A real source attached to a claim it does not support is a HIGH finding, not a pass. It never states or implies who or what wrote the document.Testare★ 64
- 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.Redactare★ 85
- reviewdzhng/skillsCloseout pass on a finished substantive change — sequence refactor-clean (shape), code-review (diff), and write-docs (docs) so all three run, in the order where each feeds the next. Use after implementing a slice or feature and before calling it done or committing; when the user asks for a final review, a cleanup-and-document pass, or to "review everything." For a diff-only audit, reach code-review directly.Inginerie★ 1.4K
- regression-testingnahid-sparktales/agent-dispatcherTurn a fixed bug into a test that fails on the old code and passes on the new one. Assert behavior at the cheapest useful level and compare old behavior without reverting unrelated work or leaving scratch files. Use after a fix or when recurring defects lack coverage; not for a new feature's test strategy or an environmental/cosmetic failure.Testare★ 59
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te