unslop-fixlisted
Install: claude install-skill RuslanAMandell/UnslopMyCode
# unslop-fix
## Overview
Applies the fix plan from `.unslop/findings.json`, split by fix class. Never
rewrites a security boundary on a guess, and never claims an action it did not
perform.
## Preconditions
1. `.unslop/findings.json` exists. If not, run `unslop-audit` first.
2. The working tree is clean. On a dirty working tree, stop and ask - an
interleaved diff is unreviewable, and unreviewable changes are the failure
mode this whole plugin exists to prevent.
3. Record whether the project's test command already passes. A failure that
predates your work must not be attributed to your commits.
4. Create and switch to `unslop/fixes`.
## Pass 1 - `auto`
Apply every `auto` finding without asking per item. **One commit per finding**,
message `fix(unslop): <ID> <short summary>`.
If a test command exists, run it after each commit. On failure: revert that one
commit, reclassify the finding as `assisted`, and keep going. Do not debug
someone else's failing test inside a fix pass.
Recipes: [references/fix-recipes.md](references/fix-recipes.md).
## Pass 2 - `assisted`
For each finding, give the user, in one message: the finding, the single
question you need answered, and the patch you will apply once answered. Batch
the questions so they can be answered in one sitting.
Never guess an ownership column, a role model, or an allowed origin. If the
answer is not in the codebase and the user has not given it, the finding stays
open and goes in the summary. A wrong RLS pol