slopmoplisted

Trigger when you would normally reach for pytest, gh, mypy, black, or other raw repo tooling. Redirect to `sm swab`, `sm scour`, `sm buff`, `sm sail`, `sm refit`, or `sm doctor` so remediation follows the established rails. Also trigger when asked to "install" or "set up" slop-mop in a repo, or when you find a repo with sm installed but no .sb_config.json — follow the install handoff (sm agent install → sm init → sm refit) before the loop. Also trigger when filing issues about slop-mop friction — use `sm barnacle file` / `/sm-barnacle`, never `gh issue create`. Also trigger when the maintenance loop is exhausted and only a human judgment call remains — use `sm wake-angry-drunk-captain` as a last resort.
ScienceIsNeato/slop-mop · ★ 3 · Data & Documents · score 69

Install: claude install-skill ScienceIsNeato/slop-mop

# Slop-mop skill > **Filing slop-mop friction?** Use `/sm-barnacle` or `sm barnacle file` — **never `gh issue create` directly**. The barnacle CLI auto-applies the correct labels and targets the right repo regardless of where you are. Slop-mop (`sm`) has two primary modes: **refit** (one-time onboarding) and **maintenance** (steady-state development). Refit remediates all existing slop and installs permanent guards; the swab/scour/buff loop then keeps the repo clean as you work. ## Setting up slop-mop in a repo (the install handoff) When the user says "install slop-mop", "set up slop-mop in this repo", or similar, do **not** improvise ad-hoc setup. It is an ordered handoff — each step is a real CLI surface (`sm -h` lists them). Run them in order, skipping any that are already done: 1. **CLI present?** If `sm` is "command not found", install the utility: `pipx install slopmop[all]`. 2. **Repo-local agent instructions?** Install them so every agent in this repo follows the rails: `sm agent install` (add `--target copilot|cursor|claude` as needed). 3. **Config?** If there's no `.sb_config.json`, generate one tuned to the detected stack: `sm init --non-interactive`. 4. **Onboard the existing code:** `sm refit --start` → `sm refit --iterate` → `sm refit --finish`, then enter the maintenance loop. "Install slop-mop in the repo" means all of the above, not just step 1. If you are unsure which steps remain, `sm sail` reads the repo state and tells you the next mo