shunk031-doc-slop-review
SolidReview reader-facing text with the repository's two-tier slop review before publishing it. Use when writing or editing documentation, README or TRAINING files, issue bodies and comments, pull request bodies and descriptions, or status reports that another person will read. Runs deterministic checks and one blind model judge over the draft, quotes each problem, and produces a PASS or FAIL to attach to the publish report; an unavailable review is a failed gate, not a PASS.
Install
Quality Score: 84/100
Skill Content
Details
- Author
- shunk031
- Repository
- shunk031/dotfiles
- Created
- 10 years ago
- Last Updated
- today
- Language
- Shell
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
slop-check
Fresh-eyes logic-and-slop review of prose and copy. Catches writing that reads like fine English but is logically, mathematically, or definitionally wrong, plus internal contradictions, off-brand drift, and AI tells. NOT a fact-checker - run it as a logic gate AFTER the facts are verified, before publishing. Triggers: 'slop check', 'slop detector', 'logic and slop review', 'check this for AI slop', 'fresh-eyes review', 'is this writing logically sound', 'review my copy before publishing', 'catch contradictions and AI tells', 'gate A'. Works on one file or many (fans out one reviewer per file). Report-only - it never edits.
antislop-review
Use when writing, reviewing, or repurposing content that ships under a person's or brand's name, especially drafts from an agency, a freelancer, or a model. Symptoms - the draft feels AI-generated, repeats "not X, it's Y" contrasts, cites studies without numbers, makes claims that would fit any company in the industry, gives a reader no reason to care today, reuses one header template across a batch, or reads fine sentence by sentence and hollow as a whole.
slop-scan
Use when the user wants to scan the current repo for AI slop, verbosity, fragile hard-coded references (line numbers, test counts, file counts), or low-value contributions in tracked files, with each finding landing as its own atomic forward-going commit. Triggers on phrases like "scan for slop", "audit repo for slop", "deslop the repo", "remove slop from this codebase", "scrub the repo", "scan the codebase for AI signatures", or "clean up slop without rewriting history". Does NOT rewrite history; every finding lands as a forward-going commit, with the project's formatter, linter, and type-checker running before each commit.