Currently the threshold is hardcoded in the system prompt: any MAJOR finding → REQUEST_CHANGES, no MAJORs → APPROVE. Different teams may want different thresholds.
Proposed Solution
Add a --threshold / REVIEW_THRESHOLD option with values like:
strict — any finding (MAJOR, MINOR, or NIT) triggers REQUEST_CHANGES
major — only MAJOR findings trigger REQUEST_CHANGES (current default)
lenient — never REQUEST_CHANGES, always APPROVE with findings noted
The threshold is injected into the system prompt rules section.
Use Cases
strict: gargoyle (zero findings policy)
major: general repos (only block on real issues)
lenient: early-stage repos where reviews are advisory only
## Problem
Currently the threshold is hardcoded in the system prompt: any MAJOR finding → REQUEST_CHANGES, no MAJORs → APPROVE. Different teams may want different thresholds.
## Proposed Solution
Add a `--threshold` / `REVIEW_THRESHOLD` option with values like:
- `strict` — any finding (MAJOR, MINOR, or NIT) triggers REQUEST_CHANGES
- `major` — only MAJOR findings trigger REQUEST_CHANGES (current default)
- `lenient` — never REQUEST_CHANGES, always APPROVE with findings noted
The threshold is injected into the system prompt rules section.
## Use Cases
- **strict**: gargoyle (zero findings policy)
- **major**: general repos (only block on real issues)
- **lenient**: early-stage repos where reviews are advisory only
Closing — this is configurable via --system-prompt-file. The default prompt defines the threshold ("any MAJOR → REQUEST_CHANGES"), and per-repo overrides can redefine severity rules. No code change needed.
Closing — this is configurable via `--system-prompt-file`. The default prompt defines the threshold ("any MAJOR → REQUEST_CHANGES"), and per-repo overrides can redefine severity rules. No code change needed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Currently the threshold is hardcoded in the system prompt: any MAJOR finding → REQUEST_CHANGES, no MAJORs → APPROVE. Different teams may want different thresholds.
Proposed Solution
Add a
--threshold/REVIEW_THRESHOLDoption with values like:strict— any finding (MAJOR, MINOR, or NIT) triggers REQUEST_CHANGESmajor— only MAJOR findings trigger REQUEST_CHANGES (current default)lenient— never REQUEST_CHANGES, always APPROVE with findings notedThe threshold is injected into the system prompt rules section.
Use Cases
Closing — this is configurable via
--system-prompt-file. The default prompt defines the threshold ("any MAJOR → REQUEST_CHANGES"), and per-repo overrides can redefine severity rules. No code change needed.