slop-mop · diff
git:20260314.2b91a56 to git:20260320.9dcc930
10 added, 6 removed. Audit A to A.
---
name: slop-mop
description: >-
Speed multiplier for long-running code generation and slop resolution —
- provides the swab/scour/buff loop so you always know what to do next.
+ provides the swab/scour/buff loop and the refit remediation rail so you always know what to do next.
---
# Slop-mop skill
Slop-mop (`sm`) is your procedural backbone for development in this repository. It accelerates long-running code generation by keeping the repo clean as you work, and it accelerates slop resolution by giving you a fast, repeatable loop that tells you exactly what to fix next.
## When to use
- **During implementation**: Run `sm swab` after every meaningful code change. Keep running until clean.
+ - **During inherited remediation**: Run `sm refit --generate-plan`, then `sm refit --continue` until the plan completes.
- **Before PR**: Run `sm scour` for a comprehensive sweep.
- **After CI/review**: Run `sm buff <PR_NUMBER>` to convert feedback into next steps.
## The loop
```
- Write code → sm swab → fix → repeat (until clean)
- ↓ ready for PR
- sm scour → fix anything remaining
- ↓ PR opened
- sm buff <PR#> → follow remediation plan
+ Normal work: write code → sm swab → fix → repeat → sm scour → sm buff <PR#>
+ Remediation: sm refit --generate-plan → fix one gate → sm refit --continue
```
## Tooling preference
- Prefer MCP tools `sm_swab`/`sm_scour`/`sm_buff` if available.
- Otherwise, run CLI commands from the project root.
+
+ ## Refit discipline
+
+ - Use `sm refit` only for remediation-phase repos.
+ - Treat `sm refit --continue` as the canonical resume command.
+ - Let `refit` own the structured remediation commits when the rail is active.
## Safety
- Never bypass or silence a failing check — that's how repo rot compounds.