mcpField
S
slopmop

slopmop

github.com/davepoonTesting & quality3.7k61 installsUpdated today
Repository

About slopmop

Slop-mop is a skill for maintaining code repositories with the `sm` CLI. It guides one-time cleanup and ongoing checks, using a workflow that turns implementation and review feedback into corrective work.

Key features

  1. 01One-time repository refit
  2. 02Guided maintenance workflow
  3. 03Checks after code changes
  4. 04Comprehensive pre-PR sweep
  5. 05Turns review feedback into tasks

Use cases

  1. 01Remediating existing repository issues
  2. 02Checking changes during implementation
  3. 03Sweeping a repository before a PR
  4. 04Converting CI or review feedback into next steps

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/davepoon/buildwithclaude --skill slopmop

After installing, type/slopmopin Claude Code to confirm it loaded.

Details

From the project README

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

Fastest path:  sm sail → fix what it finds → sm sail → repeat until PR lands
Manual path:   write code → sm swab → fix → repeat → sm scour → sm buff <PR#>

sm sail automates verb selection. Use individual verbs (sm swab -g <gate>, sm buff resolve, etc.) for surgical work.

Refit (before entering the loop)

Refit is not part of the maintenance loop. It is step 0 — how you earn the right to enter the loop.

sm refit --start → fix one gate → sm refit --iterate → ... → sm refit --finish

Prerequisite

The sm CLI must be installed in the user's environment. If invocation fails with "command not found", suggest:

pipx install slopmop[all]

Then re-run the command.

Safety

  • Never bypass or silence a failing check — that's how repo rot compounds.
  • If a gate seems wrong, tune it or file a bug. Don't disable it as a workaround.
  • Report friction (invalid guidance, broken state, blocked rails) via /slopmop:sm-barnacle rather than working around it.

Reference

Full project docs: https://github.com/ScienceIsNeato/slop-mop Workflow state machine: https://github.com/ScienceIsNeato/slop-mop/blob/main/DOCS/WORKFLOW.md Gate reasoning: https://github.com/ScienceIsNeato/slop-mop/blob/main/DOCS/GATE_REASONING.md

Comments

Markdown supported