slop-cop

Slop Cop

Run slop-cop check over a target file (or stdin) and summarize the LLM-prose-tell violations it finds: overused intensifiers, filler adverbs, negation pivots, em-dash abuse, throat-clearing, hedge stacks, metaphor crutches, and so on. This is the common-case report flow — it does not rewrite the file unless the user asks.

Resolve the binary

The plugin's SessionStart hook normally bootstraps the binary into the plugin's persistent data dir before you run, so resolution is usually instant. Pick the first option that works:

# 1. Pre-installed on PATH (the user already has slop-cop).
if command -v slop-cop >/dev/null 2>&1; then
  SLOP_COP=slop-cop
# 2. Bootstrapped into the plugin's persistent data dir (normal path).
elif [ -x "${CLAUDE_PLUGIN_DATA}/bin/slop-cop" ]; then
  SLOP_COP="${CLAUDE_PLUGIN_DATA}/bin/slop-cop"
# 3. Not yet present (hook skipped/offline): bootstrap now. The installer is
#    idempotent and prints the absolute binary path on stdout.
else
  SLOP_COP="$(bash "${CLAUDE_PLUGIN_ROOT}/scripts/install-binary.sh")"
fi

${CLAUDE_PLUGIN_DATA} and ${CLAUDE_PLUGIN_ROOT} are substituted to real paths in this skill's text. The installer downloads the host-matched binary from the latest yasyf/slop-cop release into ${CLAUDE_PLUGIN_DATA}/bin/ (a location that survives plugin updates); no Go toolchain is required. On Windows, run pwsh "${CLAUDE_PLUGIN_ROOT}\scripts\install-binary.ps1" instead — it prints the slop-cop.exe path the same way.

Run

Pick the target:

• The path the user named.
• Otherwise the file they have open / selected.
• - to read from stdin (pass --lang=markdown for prose drafts).

"$SLOP_COP" check --pretty <path>

slop-cop auto-detects the input language from the extension and masks non-prose regions before running detectors — .md / .markdown / .mdx → markdown, .html / .htm → html, .jsx / .tsx / .ts / .js → the matching tree-sitter mode (so only comments, string literals, and JSX text are scanned). Override with --lang=<mode> when needed (e.g. --lang=text to see every regex hit, --lang=markdown for stdin prose).

It prints a JSON document: {"text_length": N, "violations": [...], "counts_by_rule": {...}, "counts_by_category": {...}, "lang": "...", "llm": {...}}.

Report

Parse the JSON and present, concisely:

• The total violation count and the counts_by_category breakdown.
• One bullet per violation: the rule id, the matched span (first ~60 chars), and the suggestedChange / explanation when present.
• If there are no violations, say so plainly.

Do not paste the raw JSON unless asked. End with a short pointer: the user can ask for a revision and you will apply the canonical fixes (e.g. utilize → use, drop sentence-opening importantly / ultimately, collapse hedge stacks, replace em-dash pivots with proper punctuation, cut metaphor clichés). Only rewrite the file when the user asks for it.