Quality review Shipped

The default is the full cumulative diff from the merge-base with main through HEAD, at risk scope — asking whether there is a defect or a decision here that bites later. Narrowing the scope is a flag you pass, never something the run decides for you, because a silently narrowed review looks complete while being impossible to trust.

Typical invocations

myteams devteam review code --base main
myteams devteam review code 3:3
myteams devteam review code --repo ../other-project --security --data
myteams devteam review code --effort max --all

Flags worth knowing

• The optional positional target is its own small grammar, not a git revision range: 3 is three commits back, 3:3 is three commits forward from HEAD~3, <sha>:<sha> is an explicit pair, and a bare branch name is that branch against its base. Git’s A..B range syntax is not among them, and passing it exits with an error rather than reviewing something.
• --base <branch> — review the whole cumulative diff from the merge-base, which is the default scope of every review.
• --repo <path> — review somewhere other than the current directory.
• --effort normal | high | max — how hard each convened lane looks, and what it costs.
• --<scope> … | --all — compose scopes as a union; risk is the default.
• --fix [all | recommended] — run the fix loop afterwards, from a driving session.
• --fresh — ignore review memory and re-derive everything.
• --resume <path> — pick up an interrupted run.

Where the mechanics live

Everything about how a review actually executes — classification, scopes, selection, the verifier pillars, the consultant — is under The Pipeline. This entry is about what you type and what you get back.