slopmop

Redirects raw repo tooling commands to slop-mop CLI verbs for gated code remediation workflows.

3.4k|487|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/davepoon/buildwithclaude --skill slopmop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slopmop
Source: https://github.com/davepoon/buildwithclaude/tree/main/plugins/slopmop/skills/slopmop
Command: npx skills add https://github.com/davepoon/buildwithclaude --skill slopmop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires slopmop.

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.

Frequently Asked Questions about slopmop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run code quality checks with slop-mop?

Run `sm swab` after every meaningful code change to check quality gates, repeating until clean. Before opening a PR, run `sm scour` for a comprehensive sweep of all gates.

What is the difference between sm refit and the maintenance loop?

Refit is step 0, a one-time onboarding that remediates all existing issues and installs permanent guards via `sm refit --start`, `--iterate`, and `--finish`. The swab/scour/buff maintenance loop then keeps the repo clean during ongoing development.

How do I file an issue about slop-mop friction?

Use `sm barnacle file` or the `/slopmop:sm-barnacle` command instead of `gh issue create`. The barnacle CLI automatically applies the correct labels and targets the right repository regardless of your current location.

What should I do if the sm command is not found?

Install the slop-mop CLI with `pipx install slopmop[all]`, then re-run the command. The sm CLI must be present in your environment before any slop-mop verbs will work.

When should I use sm sail instead of individual verbs?

Use `sm sail` when unsure what to do next, since it reads workflow state and selects the right action automatically. Use individual verbs like `sm swab -g <gate>` or `sm buff resolve` for surgical, targeted work.

Can I disable a failing slop-mop gate as a workaround?

No, bypassing or silencing a failing check is explicitly discouraged because it compounds repo rot. If a gate seems wrong, tune it or file a bug through the barnacle command instead.