Run any Skill in Manus with one click

clean-sweep

Stars1

Forks0

UpdatedJuly 17, 2026 at 07:26

Exhaust a finite backlog of findings to zero, PR-per-finding, on Orca. Sources: an audit/adversarial-review document, the issue tracker, or verified false documentation claims. Each finding is skeptic-triaged (reproduced or refuted with evidence), fixed on an integration branch with a failing-first test, build-blind reviewed, merge-verified, and closed with a linked SHA; the loop re-enumerates until dry. Use when "clean sweep", "close every issue", "drain the backlog", "fix everything in this audit", "the README lies — verify and fix it", or a broken test that fails deterministically (N/N, cause findable — deflake-it routes those here). Not for security/perf/deps/coverage-gaps/flakes (those are harden-it / speed-it / modernize-it / prove-it / deflake-it — different convergence proofs) and not for building new work (ship-it).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ravidsrk

ravidsrk/orca-fleet

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	clean-sweep
description	Exhaust a finite backlog of findings to zero, PR-per-finding, on Orca. Sources: an audit/adversarial-review document, the issue tracker, or verified false documentation claims. Each finding is skeptic-triaged (reproduced or refuted with evidence), fixed on an integration branch with a failing-first test, build-blind reviewed, merge-verified, and closed with a linked SHA; the loop re-enumerates until dry. Use when "clean sweep", "close every issue", "drain the backlog", "fix everything in this audit", "the README lies — verify and fix it", or a broken test that fails deterministically (N/N, cause findable — deflake-it routes those here). Not for security/perf/deps/coverage-gaps/flakes (those are harden-it / speed-it / modernize-it / prove-it / deflake-it — different convergence proofs) and not for building new work (ship-it).
license	MIT
proof	self-run
proof_evidence	docs/runs/2026-07-13-clean-sweep-self-run.md
compatibility	HARD dependency: Orca runtime + the orchestration skill (Orca CLI). git + gh (or a tracker via orca linear). One worker playbook pack per worker (Matt triage/tdd, or Addy debug/build) — never two routers in one worker.

clean-sweep — exhaust a finite backlog to zero, with evidence

You are the COORDINATOR of a run that closes every real item in a bounded set and leaves the repo demonstrably working. Thin loop-holder: you enumerate, dispatch the per-finding pipeline, verify against authoritative state, and keep the ledger FILE (your memory is compacted; the ledger survives). You never review, code, open PRs, or merge — every one is a dispatched worker.

Read ARCHITECTURE.md once. Composes remediate-finding, acceptance-review, build-change, compound-learn; rides merge-serialization, reviewed-sha-freshness, dispatch-lifecycle, liveness-resume, evidence-manifest, orca-dag-semantics, ledger-contract, attention-budget. Review is remediate-finding's build-blind step (acceptance-review); per-finding negative control is build-change — not a full runtime-prove pass (reserved for non-trivial feature-class findings handed to ship-it).

Two terminal outcomes

DRY — full re-enumeration finds zero items not CLOSED with evidence (no open parks).
DRY-WITH-PARKED (degraded) — set exhausted except ≥1 PARKED (needs-human, CODE_CLOSED + VERIFY_AT_SCALE, etc.). Never reported as DRY.

The source (declare it — same unit, same pipeline, source-specific enumeration)

source=audit (default): findings from a scan / adversarial-review doc. FREEZE the findings list.
source=tracker: OPEN ISSUES. Record run-start T0 FIRST; the denominator is two queries — every open issue in scope (paginated to the end; a truncated listing silently fails the run) AND every issue created/reopened since T0 any state (class externally-resolved). Re-run BOTH each loop.
source=doc-claims: falsifiable documentation claims — a false claim IS a finding (extract → verify against file:symbol or a run → correct/remove). Discover claims in docs/, README, code comments, or a user-supplied list. Generating NEW docs is not this mission (that's ship-it scoped work).

Any source: a PRIOR run's completion report over the same surface is a claims list to RE-VERIFY (liveness-resume.md inflation post-mortem), never a pre-closed set — its green-but-unverified claims enter the enumeration FIRST.

Pipeline

SELF-ORIENT → ENUMERATE (per source) → SKEPTIC-TRIAGE (reproduce-or-refute) → FREEZE
  → BOOTSTRAP integration BASE (preflight --base <BASE> --fork-point <header sha>; BASE ≠ default)
  → PER-FINDING (remediate-finding: verify-real → build-change → PR → build-blind review → merge_ready)
  → conductor LAND (merge-serialization) → CLOSE with evidence
  → re-ENUMERATE (loop until dry) → FINAL REPORT + `compound-learn` + human gates

Run the coordinator as a MANUAL loop (task-create → spawn → dispatch --inject → check --wait), not orchestration run — you want the file-ledger boolean gate under your control. Dispatch waves respect attention-budget WIP.

Convergence proof (definition of done)

A full enumeration finds ZERO items that are not (a) CLOSED with evidence (a merged, ancestry-verified PR + a test that failed pre-fix, revert-audited on a ≥10% sample; the closing comment links PR + test; ledger flags BUILD_DONE…WT_CLEAN all t) or (b) PARKED with an allowed class (refuted/duplicate closes are a one-way batch gate; needs-human / CODE_CLOSED+VERIFY_AT_SCALE name their gate/OPS ref). The final enumeration output is pasted in the ledger showing the dry state. source=tracker reconciles created/closed-mid-run issues against T0, so the count is honest. Manifest names DRY or DRY-WITH-PARKED.

Ledger (header first, then rows)

Line 1 per liveness-resume.md: RUN · COORDINATOR · BASE · FORK_POINT · T0 · SOURCE · WIP (SOURCE = source type + enumeration digest). Phase marker + unit boolean flags per ledger-contract.md:

Gates + supervision

Batch human gate for refuted/duplicate closes (or a once-per-run recorded grant). Fix-backed closes need no extra gate — the evidence chain is authorization. BASE→default promotion is out of scope: open the promotion PR, stop. Stalls → liveness-resume WATCH; compaction → CONTEXT HANDOFF then RESUME; death → RESUME (ledger-scoped, git-verified).

Anti-patterns

Fixing without the triage repro (you'll "fix" symptoms and close real bugs unfixed). Closing from worker memory (only off verified merges). One mega-PR for many findings (merge-serialization exists). Truncated enumeration (partial denominator = a false "done"). Owning security/perf/deps/coverage-gaps/flakes — those are separate missions with different convergence proofs.

harden-it / speed-it / modernize-it / prove-it / deflake-it (specialist campaigns, distinct convergence proofs), ship-it (build new), review-it (verdict only), mission-scheduling (a bounded source stops at the promotion PR, so it schedules as a nightly unattended sweep).

More from this repository

same repository

oss-contribute

ravidsrk/orca-fleet

Turn a bounded set of issues on a repo you do NOT control into landed open-source contributions. Each actionable issue is skeptic-triaged (including a search of the upstream repo's OPEN PRs, not just its code), built on a fork with a failing-first test, reviewed build-blind, and opened as an etiquette-correct PR against the upstream default branch — or, where a maintainer PR already exists, shared as a quoted review-assist comment (an alternative PR only if maintainers invite one). The loop re-enumerates until the actionable set is dry. Merge is the maintainer's; the fleet never merges. Use when "contribute to this project", "open PRs for these upstream issues", "help out this OSS repo", "send fixes upstream", "we only have a fork". Not for a repo you own and can merge (that is clean-sweep — merged-SHA closure) and not for building a net-new project (ship-it).

2026-07-171

ship-it

ravidsrk/orca-fleet

Turn intent or a frozen spec into a released, verified outcome on Orca. Entry is either a frozen spec (validate → decompose) or raw intent (grill → freeze → decompose); after freeze both enter one canonical pipeline: decompose → build (tested slices) → acceptance review → runtime-prove → land → release → observe, stopping at the highest release state you're authorized to reach (BUILT / PROMOTION_READY / RELEASED / DEPLOYED_AND_VERIFIED). Use when "build and ship this", "spec to shipped product", "ship this feature", or an autonomous build-to-release run. Not for closing an existing backlog (that's clean-sweep) or a foggy goal that needs charting first (that's map-it).

2026-07-171

prove-it

ravidsrk/orca-fleet

Give every critical path a test that dies under a semantics-preserving mutation. Map the untested critical surface (coverage × call-graph of the money/auth/data paths), write characterization tests that assert real behavior, prove each earns its keep by failing at its assertion under a mutation (harness still runnable — a compile break is not proof), and route surfaced bugs to a fix or backlog, looping until every confirmed critical path is mutation-audited. Use when "close the test gap", "cover the critical paths", "test debt", characterization/mutation testing — it owns missing coverage, not broken tests. Not for flake eradication (deflake-it), a deterministically failing test (clean-sweep), or building features with tests from the start (ship-it).

2026-07-171

harden-it

ravidsrk/orca-fleet

Establish a threat model and close it: audit → prove exploits → fix → RE-ATTACK the fix and audit the whole vulnerability class → re-audit, looping until a fresh full audit finds zero unrefuted P0/P1. STRIDE + OWASP Top 10 + OWASP LLM Top 10 + supply-chain. Use when "harden this", "security sweep", "red team", "close the security loop", or an unattended audit-fix-verify security run. The full adversarial loop — for a bounded per-diff security check use review-it's risk lens. Not for general backlog drain (clean-sweep) or a single PR verdict (review-it).

2026-07-171

map-it

ravidsrk/orca-fleet

Resolve a foggy, multi-session goal into a frozen execution map that ship-it can consume — decisions, not deliverables. Chart a fog-of-war map of decision-tickets (only ticket what you can phrase sharply now), clear the research/decision frontier in parallel with HITL at each decision, and produce a frozen plan + a prepared DAG. Use when the goal is too big/foggy for one session, "chart this", "plan this epic", "I don't know the shape yet", or you can't yet authorize implementation. Its outcome is a decided plan; building is ship-it. Not for a foggy BUG (root-cause) or ready-to-build intent (ship-it).

2026-07-171

deflake-it

ravidsrk/orca-fleet

Eliminate intermittent test failures to a declared confidence contract. Detect flakes by repeat-run + CI retry history, diagnose each with a loop that RAISES the failure rate (never a theory), fix the root cause and ratchet it red-by-revert, then re-run the whole suite for a consecutive green streak — local AND in CI — looping until the streak holds. Retry-wrappers as fixes are banned and grep-checked. Use when "kill the flaky tests", "deflake the CI", "flake zero", a flaky/intermittent suite. Not for a single hard bug with no suite-rate contract (root-cause) or deterministic failures (clean-sweep).

2026-07-171

name	clean-sweep
description	Exhaust a finite backlog of findings to zero, PR-per-finding, on Orca. Sources: an audit/adversarial-review document, the issue tracker, or verified false documentation claims. Each finding is skeptic-triaged (reproduced or refuted with evidence), fixed on an integration branch with a failing-first test, build-blind reviewed, merge-verified, and closed with a linked SHA; the loop re-enumerates until dry. Use when "clean sweep", "close every issue", "drain the backlog", "fix everything in this audit", "the README lies — verify and fix it", or a broken test that fails deterministically (N/N, cause findable — deflake-it routes those here). Not for security/perf/deps/coverage-gaps/flakes (those are harden-it / speed-it / modernize-it / prove-it / deflake-it — different convergence proofs) and not for building new work (ship-it).
license	MIT
proof	self-run
proof_evidence	docs/runs/2026-07-13-clean-sweep-self-run.md
compatibility	HARD dependency: Orca runtime + the orchestration skill (Orca CLI). git + gh (or a tracker via orca linear). One worker playbook pack per worker (Matt triage/tdd, or Addy debug/build) — never two routers in one worker.

clean-sweep — exhaust a finite backlog to zero, with evidence

Two terminal outcomes

DRY — full re-enumeration finds zero items not CLOSED with evidence (no open parks).
DRY-WITH-PARKED (degraded) — set exhausted except ≥1 PARKED (needs-human, CODE_CLOSED + VERIFY_AT_SCALE, etc.). Never reported as DRY.

The source (declare it — same unit, same pipeline, source-specific enumeration)

source=audit (default): findings from a scan / adversarial-review doc. FREEZE the findings list.
source=tracker: OPEN ISSUES. Record run-start T0 FIRST; the denominator is two queries — every open issue in scope (paginated to the end; a truncated listing silently fails the run) AND every issue created/reopened since T0 any state (class externally-resolved). Re-run BOTH each loop.
source=doc-claims: falsifiable documentation claims — a false claim IS a finding (extract → verify against file:symbol or a run → correct/remove). Discover claims in docs/, README, code comments, or a user-supplied list. Generating NEW docs is not this mission (that's ship-it scoped work).

Pipeline

SELF-ORIENT → ENUMERATE (per source) → SKEPTIC-TRIAGE (reproduce-or-refute) → FREEZE
  → BOOTSTRAP integration BASE (preflight --base <BASE> --fork-point <header sha>; BASE ≠ default)
  → PER-FINDING (remediate-finding: verify-real → build-change → PR → build-blind review → merge_ready)
  → conductor LAND (merge-serialization) → CLOSE with evidence
  → re-ENUMERATE (loop until dry) → FINAL REPORT + `compound-learn` + human gates

Convergence proof (definition of done)

Ledger (header first, then rows)

Line 1 per liveness-resume.md: RUN · COORDINATOR · BASE · FORK_POINT · T0 · SOURCE · WIP (SOURCE = source type + enumeration digest). Phase marker + unit boolean flags per ledger-contract.md: