What problem does it solve?
Developers often bypass established quality gates by running raw tools like pytest, mypy, or gh directly, which fragments remediation workflows and lets repo rot accumulate. This Skill intercepts those impulses and routes them through the slop-mop (sm) CLI so every check, fix, and issue follows the project's established rails.
Core Features & Use Cases
- Tool redirection: Replaces direct invocations of pytest, gh, mypy, and black with
sm swab, sm scour, sm buff, sm sail, sm refit, or sm doctor.
- Workflow state automation:
sm sail reads workflow state and selects the right action, while sm refit handles one-time onboarding remediation before entering the maintenance loop.
- Structured issue filing: Routes slop-mop friction reports through
sm barnacle file or /slopmop:sm-barnacle instead of gh issue create, applying correct labels and targeting the right repo.
- Use Case: After finishing a code change, instead of running pytest manually, run
sm swab to check all quality gates, then sm scour before opening a PR and sm buff <PR_NUMBER> to convert CI and review feedback into next steps.
Quick Start
Ask the assistant to run sm sail to check the current workflow state and determine the next remediation step for the repository.