shunk031-doc-slop-review

Solid

Review 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.

AI & Automation 151 stars 6 forks Updated today MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
73
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Document Slop Review ## 読了時の応答 - この skill を読んだら、`🧹 私は shunk031-doc-slop-review を読みました。` と応答する。 ## The command Run `scripts/doc_slop_review.py` from the dotfiles repository checkout: ```bash cd "$(chezmoi source-path)" # typically ~/.local/share/chezmoi uv run --python 3.14.6 --no-project python scripts/doc_slop_review.py DRAFT.md ``` Give this command to the user when you report the work. Do not paraphrase it and do not ask the reader to reconstruct it from a description. ## When to use Run this before publishing any text a person will read: repository documentation, `README.md` and `TRAINING.md` style files, issue bodies and comments, pull request bodies, and status or completion reports. Skip it for code-only changes, machine-readable data, and ordinary conversational replies. A commit message body is optional; review it when it carries the explanation a reader depends on. ## Flow 1. Write the draft to a file, or pipe it in. Do not publish first and review after. 2. Run the review on the draft with the command above. 3. Address every finding, or state why a finding does not apply. A finding you disagree with is answered in the report, not ignored silently. 4. Re-run until the complete two-tier review reports PASS, then attach that verdict to the publish report. A deterministic-only PASS (including `--skip-model`) is not a complete review and is not permission to publish. 5. Treat exit code `2` as a failed review that blocks publication. This incl...

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

Data & Documents Listed

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.

0 Updated today
dzivkovi
Code & Development Listed

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.

0 Updated 4 weeks ago
borek707
AI & Automation Listed

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.

2 Updated 6 days ago
tony