slop-mop

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.

Substitutes pytest, gh, mypy, black, and every other tool in this repo with a single `sm` CLI. Never run the underlying tools directly — `sm swab` for fast iteration, `sm scour` before a PR, `sm buff` after CI or review feedback, `sm doctor` when the environment looks broken, `sm refit` for onboarding existing repos, `sm sail` when unsure what to do next. Use `sm barnacle file` (never `gh issue create`) when slop-mop itself causes tool friction — the barnacle CLI auto-applies labels and targets the right repo.

Speed multiplier for long-running code generation and slop resolution — provides the swab/scour/buff loop and the refit remediation rail so you always know what to do next.