unslop

When to invoke

Use when: "unslop", "humanize this", "de-ai this", "this reads like a bot", "make it sound like me", "clean up the prose before I post it", or when a README, CHANGELOG entry, release note, PR body or article draft needs a voice pass before it goes public.

Preamble

eval "$(~/.vibestack/bin/vibe-slug 2>/dev/null)" 2>/dev/null || SLUG="unknown"
_LEARN_FILE="${VIBESTACK_HOME:-$HOME/.vibestack}/projects/${SLUG:-unknown}/learnings.jsonl"
if [ -f "$_LEARN_FILE" ]; then
  _LEARN_COUNT=$(wc -l < "$_LEARN_FILE" 2>/dev/null | tr -d ' ')
  echo "LEARNINGS: $_LEARN_COUNT entries loaded"
  if [ "$_LEARN_COUNT" -gt 5 ] 2>/dev/null; then
    ~/.vibestack/bin/vibe-learnings-search --limit 5 2>/dev/null || true
  fi
else
  echo "LEARNINGS: none yet"
fi

{{include lib/snippets/session-host.md}}

{{include lib/snippets/decision-brief.md}}

{{include lib/snippets/working-protocols.md}}

{{include lib/snippets/state-protocols.md}}

User-invocable

When the user types /unslop, run this skill. /unslop --report <input> lists hits and stops; /unslop <input> lists hits and rewrites.

---

Step 1: Take the input

Accept one of three forms and normalise it to a numbered text buffer so every hit can cite a line.

Make a private run directory first and note the path it prints. Every later command in this run uses that literal path — the shell variable does not survive between commands:

RUN=$(mktemp -d "${TMPDIR:-/tmp}/unslop.XXXXXX") && chmod 700 "$RUN" && echo "$RUN"

• File path. Read the file. Note whether git tracks it, because that decides how Step 5 writes back: git ls-files --error-unmatch <path> >/dev/null 2>&1 && echo TRACKED || echo UNTRACKED
• PR number. Pull the body into the run directory: gh pr view <n> --json body -q .body > "<run>/input.md". Work on that file.
• Pasted text. Write it to <run>/input.md so the same commands apply.

The names inside the run directory are fixed: input.md for a PR body or pasted text, rewrite.md for the rewrite, facts-orig.txt and facts-new.txt for Step 4. A file path is read where it lives; its rewrite still goes to <run>/rewrite.md. Two runs at once get two directories and cannot overwrite each other, and Step 5 deletes the directory when the run ends.