review-panel
Review panel
Run the pipeline: scope → brief → panel → merge → triage → findings report → approval gate → fix → verify → final report.
Set the approval mode when the run starts. The default is gated. /review-panel auto-fix sets auto-fix, which grants standing approval for findings triaged with a fix disposition. Auto-fix never selects an escalate fork; escalations always require a later user decision.
1. Scope
Resolve one review scope for the whole panel. A user-named scope may be a pull request, commit or range, branch against a base, diff, staged or unstaged work, or named files. Use it exactly and do not add adjacent changes. If the user supplies no scope, use the first non-empty scope below:
- staged changes
- unstaged and untracked changes
- commits ahead of the upstream (
@{upstream}..HEAD) - the current branch against its merge base with the default branch
When staged changes win while unstaged edits exist, name the excluded files in the brief so no voice flags code that is mid-edit.