Skip to content

imMamdouhaboammar/anti-slop-engineering / skills/root-fix-gate

root-fix-gate

Verified

Use when a coding agent is about to patch the same symptom across controllers, views, endpoints or files; a small behavior change causes a wide diff; a workaround may hide a wrong model, schema or domain boundary; or a user proposes a shortcut with uncertain downstream effects. Trace the causal owner and compare a coherent root correction against distributed patches before implementation or review. Skip narrow, localized fixes with an already established owner.

FileKindSize
SKILL.mdskill md8.2 KB
agents/openai.yamlconfig326 B
evals/scenarios.jsonconfig6.7 KB
examples/email-checkout-record.jsonconfig1.6 KB
references/ownership-model.mdmarkdown4.8 KB
references/record-contract.mdmarkdown2.7 KB
usecases/review.mdmarkdown2.0 KB
usecases/trace.mdmarkdown3.7 KB

usecases/review.md

View on GitHub
# Review the change surface

1. **Compare planned with observed paths.** Capture `git diff --name-status <base>` and untracked changes. Inspect the real hunks, not only filenames or a score.
2. **Classify each path.** Owner, dependent consumer, migration, test, integration. Demand a causal explanation for an unexpected category. Multiple files may be required by a correct schema or API change.
3. **Search for symptom fan-out.** Look for repeated filters, checks, transformations or null-handling across controllers, handlers and views. Ask whether a single owner can enforce the same contract. Avoid centralization where semantics actually differ.
4. **Challenge root-only shortcuts.** Check whether moving code upstream could break identity, transaction ordering, authorization or context-specific behavior. A root fix that silently violates consumers is not a root fix.
5. **Check test oracles.** Tests should fail under the original bug or a realistic mutation, protect the owner invariant, and exercise affected consumers. Don't weaken old assertions to make refactors pass.
6. **Check data/authority.** A nullable field, a data deletion, and a production migration are separate decisions. Inspect recovery and explicit approval for irreversible actions; the JSON audit cannot grant authority.
7. **Revise or complete.** If the owner remains wrong, reopen investigation. If the wider diff is justified, record why and finish. If evidence is missing, say `NOT VERIFIED` and pause risky execution.

## Optional deterministic guard

From a repository containing `scripts/root_fix_guard.py`:

```bash
python3 scripts/root_fix_guard.py audit path/to/record.json --json --base HEAD --repo .
```

The audit compares `planned_changes[].path` to changed tracked and untracked paths. `UNPLANNED_CHANGE` and `WIDE_CHANGE_SURFACE` are **review** findings, never proof of bad architecture. An unavailable Git ref is an input error, not a clean diff. Inspect the actual hunks and source evidence before assigning an engineering verdict.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall