CLI commands
One page per command, each written against what the command actually prints rather than against its help text.
Every command redline --help prints. Most act on the repository you are standing in; sync, registry and metrics act on the estate instead, and running them in a product repo is a wasted afternoon rather than an error message. For what any of it is for, start with What success looks like, which walks them in the order you would reach for them; for who may run what, under which credential, see Who runs what.
redline init →
Onboard a repository: standards, security floor, merge gate, registration. The one command a product repo runs.
redline verify →
Check a repository still matches what its .redline.json claims — and, with --gate, act as the Azure gate itself.
redline remove →
Takes Redline back out of a repository, as a pull request — removing only what it can prove it wrote, and leaving the security floor alone.
redline sync →
Lands the current standards on every registered repository as a pull request, from the register derived nightly off the estate.
redline policy →
Evaluates the rules a checker can decide, with no model call — a ticket reference is present or it is not.
redline exempt →
Decides whether a pull request carries a valid exemption for a failing process check — a reason, a scope and an expiry, not a bare label.
redline review →
Reviews a change against only the rules that apply to the files it touches — locally, in either engine, before you push.
redline status →
What is installed here, how hard it bites, what an administrator still owes you, and whether the standards have moved on — from the checkout alone, with no credential.
redline explain →
What a rule means, who decided it, which files it is scoped to and which profiles receive it — the bracketed id in a finding, turned back into the line a human edits.
redline registry →
Derives the register of onboarded repositories by walking the org, from the .redline.json each one carries. Nothing about it is hand-maintained.
redline metrics →
The estate's measurement plane as eight subcommands — collect, dashboard, digest, inbox, baseline, roi, correlate and score-seeds — each with a validated flag surface over the runner it drives.