Crossfire
Fire forge's multi-lens review wave - parallel independent lenses plus a different-model worker over one change. Use when a stop gate says a review wave is owed, or the user asks for crossfire or the review wave by name. Reviews of a branch, a PR, or changes since a commit belong to other review skills. Skip when your own prompt names a run dir and a brief to follow: you are inside a run that fires this wave itself.From its SKILL.md
npx -y skills add alp82/forge --skill crossfireAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
5.3 KB, as published. Nobody here has run it
crossfire — the review wave
You are the orchestrator of one review wave: every applicable lens fired in parallel over the same change, each writing its own findings file, none seeing another's verdict before its own is written. You spawn, collect, and relay — you never review inline. Inside a forge run, forge's router fires this same wave off these same lens briefs; this skill is the standalone verb — /crossfire over whatever the user points it at.
Spawn contract (same as forge's): spawn a fresh isolated agent with the tier the roster names and the prompt: "Read <lens brief path> and follow it. Run dir: <run dir>. Inputs: <paths>." Brief paths are siblings of this file; the worker forwarder sits at ../forge/WORKER.md. Paths, never pasted content. The worker forwarder alone takes one extra field — host-vendor: <vendor>, read verbatim from the session-start banner's host-vendor line — so it can exclude same-vendor second opinions; no banner line, forward nothing and it fails loud to single-model judgment (forge's spawn contract owns this rule).
Open the scope
- Ensure
.forge/is in the repo's.gitignore; append it if missing. Create the run dir.forge/<slug>/— a short kebab-case reduction of the review subject (≤40 chars). - Resolve what's under review, in order of what the user gave: named files or directories; a commit range or PR; otherwise the working diff vs HEAD, or — tree clean — the branch diff vs the merge-base with the default branch.
- Write
receipt.md: the file list and one line on how it was derived. When the user stated a purpose, or the change traces to a tracker ticket (read it perdocs/agents/issue-tracker.md), writeintent.mdtoo. Aplan.mdexists only inside a forge run — lenses treat it as optional.
Pick the lenses
- Standing, every wave: CORRECTNESS (tier
large), ACCEPTANCE (large), SIMPLICITY (standard), SHAPE (standard), CONVENTIONS (standard). ACCEPTANCE stands down when nointent.mdexists — where nothing was promised, there is nothing to accept. - Conditional, by trigger: UI (
standard) when the diff touches user-facing UI; SECURITY (large) when it touches auth, secrets, permissions, or untrusted input; PERFORMANCE (large) when it touches a hot path or data-volume-sensitive code. - Worker: the WORKER.md forwarder (
standard), call sitecrossfire— one more lens from a different model →findings-worker.md. Its failure is visible and non-blocking.
The correctness × security overlap is deliberate, never to be tidied: SECURITY is trigger-gated, so CORRECTNESS's injection checks are the only injection coverage on a wave whose triggers didn't fire. This standing list is deliberately unconditional - standalone crossfire has no triage and no bands, so forge's size- and risk-keyed wave and this list diverge by design; never resync them.
Fire the wave
Spawn every picked lens in parallel, each reading receipt.md plus intent.md/plan.md where present, each writing findings-<lens>.md in the run dir. No lens reads another's findings file, and the worker never reads any — independence is the wave's whole value.
Collect
Backstop first. A lens that returned its findings as text without leaving findings-<lens>.md on disk gets that file written by you, from the text it returned, before collection proceeds - the review debt settles on the file, never on the return.
Read each RETURN block (fall back to the artifact when a return is malformed). Relay one table — lens | verdict | gist — then the findings that matter, confidence tags intact: [likely] is evidence-based, [unsure] is judgment; the briefs' shared reporting bar has already filtered speculative noise, so don't re-filter, just present. fail (or ACCEPTANCE's partial) blocks; warn is real but non-blocking; pass is clean.
Fix or hand off
Standalone, any lens blocking: offer the fix, don't presume it. On the user's confirm, spawn ../forge/FIXER.md (tier standard; ultra when the fix set is large or structural) with the findings paths and receipt.md. It returns a re-run set — re-spawn exactly those lenses (CORRECTNESS always rides along) over the new diff; loop until every lens is clean. Findings the fixer can't own surface to the user, never silently dropped. Inside a forge run, forge's router owns this loop instead.
Close with a terse summary: verdict per lens, what was fixed, what remains. Post the ticket resolution when the scope came from a ticket. Run artifacts are process debris — they die with the run; reasoning worth keeping goes to a repo-native home and gets pointed at.
Standing stances
- Confirm before remote. No push, publish, or PR creation without an explicit user confirm.
- Confirm before destruction. Destructive or irreversible commands are proposed, never run unconfirmed.