Reference: Review and apply

Reference for the "Review and apply" group of qargi commands: every verb with its arguments, options and examples, generated from the release.

Updated 2026-11-05

qargi review #

Check what an agent returned and put it on a task branch.

Verb	What it does
`check`	Check what a run returned: numbered patches, messages, manifest, groups
`apply`	Apply a collected, checked run to a task branch of the repository

qargi review check #

qargi review check OUT [OPTIONS]

Check what a run returned: numbered patches, messages, manifest, groups.

OUT is the member's output directory (RUN_DIR/out); the patches are read from OUT/patches only, where review apply reads them. Refuses a monolithic patch, a commit without a message body and a manifest that does not match the patches. A review run passes with a report.md (or PREFIXreport.md, as in a team run) that has a Findings section instead of patches. Prints OK, WARN or FAIL lines and a summary; exit 1 when any line is FAIL (warnings alone exit 0).

Option	Argument	What it does
`--allow-empty`		accept a manifest with no commits (a team member that was blocked or had nothing to change)

qargi review apply #

qargi review apply [RUN_DIR] [OPTIONS]

Apply a collected, checked run to a task branch of the repository.

Refuses a run applied already, and unless review check passes for RUN_DIR/out (warnings allowed) and local verify accepts the run (a refs-changed result prints the diff). Creates the branch at the commit the run's base branch had when the run was prepared and applies every patch of out/patches in order with git am, in a temporary worktree of the project's repository: your checkout is never touched and no other ref changes. The committer is the one the repository has configured, else the author of the patches. It refuses a branch that exists; a patch that does not apply removes the worktree and the branch and names the patch. On success it prints the commits and the next commands, and records branch and tip in RUN_DIR/applied and the branch in the run's ref snapshot, so local clean still accepts the run. --from-saved ID applies from <state>/runs/ID instead (refused while the run directory exists): review check of the saved OUT, local verify --saved ID, the registry's repository, slug and base, and the record in the saved copy, so it is applied once.

Option	Argument	What it does
`--project`	`PROJECT`	the project, instead of the one inferred from here
`--branch`	`BRANCH`	the branch to create (default agent/<slug> of the run)
`--from-saved`	`ID`	apply the copy local verify saved of a passed run whose directory is gone (ID: qargi.XXXXXX), with the same checks

qargi review apply ./run
qargi feature merge search agent/fix-names
qargi local clean ./run

qargi team #

Run a task with a lead and role agents (opt-in).

For a change that affects usage: the build member changes the code, the write member updates the operational docs, the review member judges both. The lead is this Claude Code session, a cloud lead, or a session started in the console; all follow the lead contract. Each member returns its own series against its own base.

Verb	What it does
`brief`	Print the brief a lead needs for one task
`check`	Check a collected team run: every member and the lead's report
`contract`	Print the lead's contract

qargi team brief #

qargi team brief [PROJECT] TEAM [OPTIONS]

Print the brief a lead needs for one task.

PROJECT can be left out inside the project's repository, or set QARGI_PROJECT.

Option	Argument	What it does
`--task`	`TEXT`	what to do
`--done`	`COMMAND`	an executable check for the builder's part
`--base`	`BRANCH`	the builder's base branch (needed when the project says @dispatcher)
`--write-done`	`COMMAND`	the writer's check
`--review-done`	`COMMAND`	the reviewer's check

qargi team check #

qargi team check RUN_DIR

Check a collected team run: every member and the lead's report.

qargi team contract #

qargi team contract

Print the lead's contract.

The procedure every lead follows, whoever it is.