Slop-mop skill

Filing slop-mop friction? Use /slopmop: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.

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.

The maintenance loop