spectre-clean

clean

End-to-end cleanup utility. The primary owns scope, risk assessment, sequencing, and synthesis. It is not a Ship dependency; phase work uses spectre-prune, spectre-test, and spectre-sweep.

Inputs

• $ARGUMENTS — optional scope hint: commit/SHA, unstaged/staged, context/session, task dir, files, or --orchestrated when a parent workflow owns the next step.
• FEATURE_ROOT — explicit feature name/root or one descendant feature artifact.

Working Set

• Reuse a managed FEATURE_ROOT only when explicit/current-thread evidence ties it to this work (physical directory wins; never branch/recency/lifecycle/scans); distinct work ignores ambient roots. Otherwise, including on collision, standalone MUST first load and follow Skill(spectre-feature-root) through DONE; orchestrated calls escalate. Keep writes beneath it and pass it unchanged.
• Resolve the same full working set used by prune/test/sweep from committed changes, staged, unstaged, and untracked files. If a provided ref/scope is invalid or ambiguous, stop and ask.
• Keep the resolved file set and primary's compact P0-P3 risk plan in-thread; write no working-set/lifecycle artifact.

Outputs + DONE

• Parallel prune and one test-lead result; manual-review/cross-boundary items preserved.
• Primary P0-P3 risk plan, compact check results, one Sweep verification/commit boundary, and CLEANED_THROUGH_SHA.
• Final report: prune/manual review · risk tiers · tests/affected checks · routed findings · sweep commits · CLEANED_THROUGH_SHA · NEEDS_AUTHORITY, if any.
• DONE when: every phase ran in its owning subagent, the primary supplied risk tiers, repairable findings were repaired/routed by their owner, manual-review items surfaced, and sweep committed or returned genuine NEEDS_AUTHORITY.

Method / guardrails

1. Resolve scope once. Establish files and feature root. Keep dynamic details out of the prompt body; read them live.
2. Primary risk assessment. Classify every resolved file P0-P3:
   • P0: auth/payment/security/crypto/session/token, PII/permissions/user-data mutation, external handlers, DB migrations, @critical.
   • P1: feature components, API/state/business logic, fetch/cache, user-visible errors.
   • P2: exported real-logic utilities, validators, transformers, adapters, hooks.
   • P3: docs/styles/config/types/constants/barrels/pass-throughs/generated files. Keep a compact plan in-thread: - [P{tier}] {file}: {behavior or SKIP reason}.
3. Parallel phases. In one dispatch, start one prune lead for Skill(spectre-prune) and one test lead for Skill(spectre-test) with the unchanged resolved set, {FEATURE_ROOT}, and the risk plan. Each uses --orchestrated; the test lead owns any internal tester batching. They return compact changed-path/check results, manual-review items, and cross-boundary needs; neither stages nor commits.
4. Sweep phase. Dispatch a sweep lead with the unchanged set and compact phase results. Skill(spectre-sweep) runs only stale/uncovered integrated checks, repairs attributable failures, and is the sole pre-rebase commit owner.
5. Synthesize. Route repairable/cross-boundary findings to their owner; report final state, the Sweep commit CLEANED_THROUGH_SHA, routed findings, and genuine authority/safety impasses.