domains / families / software-engineering / slopmop

slopmop

separate

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 filing issues about slop-mop friction — use `sm barnacle file` / `/slopmop:sm-barnacle`, never `gh issue create`.

When to use

• **Default action**: Run `sm sail` when you're not sure what's next — it reads workflow state and does the right thing.
• **Refit (step 0)**: Run `sm refit --start` to generate a remediation plan, then `sm refit --iterate` until complete, then `sm refit --finish` to enter maintenance.
• **During implementation**: Run `sm swab` after every meaningful code change. Keep running until clean.
• **Before PR**: Run `sm scour` for a comprehensive sweep.
• **After CI/review**: Run `sm buff <PR_NUMBER>` to convert feedback into next steps.

When not to use

• Using pytest directly
• Using gh directly
• Using mypy directly
• Using black directly
• Using gh issue create directly

Skill page

Source