sweep git:20260910.b5c8369A

Immutable. This exact content never changes and is served at /api/v1/blob/664b92f8cbff6c90.

---
name: sweep
description: Use only when someone explicitly invokes $hope:sweep in Codex, /hope:sweep in Claude Code, or the host's Hope Sweep command for behavior-preserving codebase cleanup.
---

# Hope Sweep

Apply proven maintenance to operating code and directly supporting tests,
configuration, build logic, documentation, examples, and assets. Read
`../write/references/writing-standard.md` for user-facing language.

## Invocation and scope

Require explicit namespaced invocation. An ordinary cleanup request or a
follow-up such as “do that” uses the ordinary workflow. If selected implicitly,
continue that request without activating Sweep.

Use the named repository, or the current one, and the whole repository unless
the person narrows it. Record the revision and working-tree state; preserve
unrelated edits and project instructions. Invocation authorizes reversible
local edits in this scope, not commits, pushes, pull requests, or merges.

## Prove and apply cleanup

Establish current behavior from running code and configuration. Follow the
actual consumers and boundaries relevant to each proposed cleanup.

Remove dead code, duplication, needless branches or wrappers, misplaced
abstractions, and repeated work. Share logic only when behavior, ownership,
and reasons to change match. Optimize only for a plausible workload with a
concrete benefit.

Prove a removal has no remaining consumer, including external or dynamic use
where relevant. A missing text reference alone does not prove safety. Remove
dedicated tests, documentation, generation, configuration, and assets with
their obsolete consumer; retain support for remaining paths.

Apply small coherent batches. Leave bugs, public-contract or behavior changes,
product and compatibility decisions, migrations, dependency changes, and
uncertain removals outside Sweep. Do not turn those signals into unsolicited
findings or follow-up tasks.

## Verify and finish

Verify affected consumers with the narrowest useful tests, checks, builds, or
runtime observations, plus required project checks. Add tests only when needed
to protect the refactor. Correct or revert regressions Sweep introduced; do not
repair pre-existing failures or widen scope during verification.

Finish when the supported cleanup is complete and affected behavior has been
checked. Report the cleanup, supporting material changed with it, and any
verification limits. If no proven cleanup exists, say so. Keep unrelated
signals out of the report.