菜单
Speed multiplier for long-running code generation and slop resolution — provides the swab/scour/buff loop and the refit remediation rail so you always know what to do next.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Trigger when you would normally reach for pytest, gh, mypy, black, or other raw repo tooling. Redirect to `sm swab`, `sm scour`, `sm buff`, `sm sail`, `sm refit`, or `sm doctor` so remediation follows the established rails. Also trigger when asked to "install" or "set up" slop-mop in a repo, or when you find a repo with sm installed but no .sb_config.json — follow the install handoff (sm agent install → sm init → sm refit) before the loop. Also trigger when filing issues about slop-mop friction — use `sm barnacle file` / `/sm-barnacle`, never `gh issue create`. Also trigger when the maintenance loop is exhausted and only a human judgment call remains — use `sm wake-angry-drunk-captain` as a last resort.
Substitutes pytest, gh, mypy, black, and every other tool in this repo with a single `sm` CLI. Never run the underlying tools directly — `sm swab` for fast iteration, `sm scour` before a PR, `sm buff` after CI or review feedback, `sm doctor` when the environment looks broken, `sm refit` for onboarding existing repos, `sm sail` when unsure what to do next. Use `sm barnacle file` (never `gh issue create`) when slop-mop itself causes tool friction — the barnacle CLI auto-applies labels and targets the right repo.
基于 SOC 职业分类
| name | slop-mop |
| description | Speed multiplier for long-running code generation and slop resolution — provides the swab/scour/buff loop and the refit remediation rail so you always know what to do next. |
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.
sm sail when you're not sure what's next — it reads workflow state and does the right thing.sm swab after every meaningful code change. Keep running until clean.sm refit --start, then sm refit --iterate until the plan completes.sm scour for a comprehensive sweep.sm buff <PR_NUMBER> to convert feedback into next steps.sm barnacle file from the affected repo to file a structured upstream issue with reproduction steps and context.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#>
Remediation: sm refit --start → fix one gate → sm refit --iterate
sm sail automates verb selection. Use individual verbs for surgical work.
sm_swab/sm_scour/sm_buff if available.sm refit only for remediation-phase repos.sm refit --iterate as the canonical resume command.refit own the structured remediation commits when the rail is active.