Mesteriis Multi-Agent PR Review
Review a Git-backed change set with bounded read-only reviewers.
Workflow
- Resolve the exact base and head, or state that the current working tree is the target.
- Read repository instructions and relevant changed files.
- If subagent tools are available, dispatch independent read-only reviewers: security, runtime bugs, tests/flakiness, maintainability/architecture, performance, and UI/UX only when frontend files changed.
- If subagents are unavailable, run the same categories sequentially.
- Merge results with
subagent-result-merge.
Reviewer Contract
Each reviewer returns:
- finding
- severity
- evidence with file/line
- confidence
- suggested minimal fix
- validation gaps
Rules
- Do not edit files.
- Do not report style-only issues unless they hide a real risk.
- Mark unverified concerns as uncertainty.
- Use
security-routerfor deep security workflow when security findings are material.