forcing agentic coder's path of least resistance through long-term maintainable codepaths
Command
Part of slopmop
Use when sm itself gives invalid guidance, blocks valid work, produces confusing output, or breaks install/upgrade/refit flow. Do not use this for real target-repo failures; fix those through the normal rail.
Command
Part of slopmop
You usually don't run buff directly — run sm sail. sm sail drives the whole PR to green and calls buff watch / triage for you, stopping only when it needs you to act (see /sm-sail). Reach for sm buff here only for surgical work: inspecting a specific failure, or resolving a single review thread when sail has parked on…
Command
Part of slopmop
Run when you find a repo with sm installed but no .sbconfig.json — or after upgrading slopmop to pick up new gates.
Command
Part of slopmop
Run slop-mop's one-time onboarding remediation rail for this repository.
Command
Part of slopmop
Command "sm-sail" from ScienceIsNeato/slop-mop, covering /sm-sail — drive a pr to green, autonomously, the loop, when sail parks on review threads, when to stop before "pr ready" — only two reasons and expect convergence, not one pass.
Command
Part of slopmop
Run slop-mop's comprehensive pre-PR sweep for this repository.
Command
Part of slopmop
Run slop-mop's iterative development loop for this repository.
Command
Part of slopmop
The last-resort verb. Use it ONLY when the loop is genuinely exhausted: barnacles filed, gates green or truly unfixable, and the single remaining move is a human judgment call no sm verb can make for you.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: