gh0stinthemirr0r/gaeos-creator/slop-repair

Repair loop for the repo's anti-slop quality gate. The gate is default-FAIL: a change is not done while slop_gate reports findings on the files it touched.

Process

1. Scope the target

Gate only the files the current change touched or created, never the whole legacy corpus. Build the list from git status --porcelain / git diff --name-only <base>...HEAD, filtered to what exists. If the user named a path, use that instead.

2. Run the gate

python3 scripts/slop_gate.py scan <path>

Use code or prose alone when the target is only one kind. The command prints findings and writes a JSON evidence artifact under evidence/slop/. Exit 0 means green; stop there.

3. Fix code findings

For ai-slop, format, and lint engine issues, try the deterministic fixer first:

node references/aislop/dist/cli.js fix <path>

Review what it changed (git diff) before keeping anything. Fix remaining findings by hand: delete dead code, replace vague names, remove TODO scaffolding, cut duplicated helpers. Do not silence findings with suppressions.

4. Fix prose findings

Follow the humanizer skill for the rewrite itself. Hard-severity findings (chatbot artifacts, cutoff disclaimers, sycophancy) are deleted outright, not reworded. For soft findings: preserve every fact from the source, cut the pattern, keep the register. Never invent facts to replace a vague claim.

Common mechanical fixes:

• em/en dashes: replace with period, comma, colon, or parentheses
• inline-header lists (- **Header:** text): rewrite as plain sentences or plain list items
• significance puffery and rule-of-three: state the concrete fact and stop
• signposting ("Let's dive in"): delete and start with the content

5. Re-run and record

Re-run step 2 on the same paths. Repeat steps 3-4 until the gate exits 0. When the change belongs to an OpenSpec change id, attach the passing artifact:

python3 scripts/evidence_gate.py pass <change-id> <req> --evidence evidence/slop/<artifact>.json

Constraints

• Do not edit files outside the change's scope to make numbers look better.
• Do not raise --max-findings / lower --min-score to pass; fix the content instead. A threshold change needs the user's explicit sign-off.
• Quoted text, code blocks, and frontmatter are out of scope for prose rewrites.