Slopmop

Name: Slopmop
Author: davepoon

davepoon/buildwithclaude

47 installs
3.2k repo stars
Updated August 2, 2026
davepoon/buildwithclaude

Redirects raw repo tooling (pytest, gh, mypy, black) to the slop-mop CLI verbs that remediate slop and keep a repo clean through refit and maintenance loops.

About

Wraps repo hygiene work behind slop-mop verbs (swab, scour, buff, sail, refit, doctor) for one-time onboarding remediation and a steady-state maintenance loop. A developer uses it to run gated cleanup after code changes and before PRs instead of invoking raw tools directly.

sm sail auto-selects the right verb from workflow state
File friction with sm barnacle, never raw gh issue create

Slopmop by the numbers

47 all-time installs (skills.sh)
Ranked #595 of 1,354 Code Review & Quality skills by installs in the Skillselion catalog
Data as of Aug 3, 2026 (Skillselion catalog sync)

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

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/davepoon/buildwithclaude/slopmop.svg)](https://skillselion.com/skills/davepoon/buildwithclaude/slopmop)

Installs	47
repo stars	★ 3.2k
Last updated	August 2, 2026
Repository	davepoon/buildwithclaude ↗

What it does

Redirects raw repo tooling (pytest, gh, mypy, black) to the slop-mop CLI verbs that remediate slop and keep a repo clean through refit and maintenance loops.

Files

SKILL.mdMarkdownGitHub ↗

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