fix(#45): tighten review verdict criteria for medium findings#49
fix(#45): tighten review verdict criteria for medium findings#49fullsend-ai-coder[bot] wants to merge 2 commits into
Conversation
Replace the subjective "multiple medium-severity findings which could affect the intended outcome" criterion with an objective rule: two or more medium findings, at least one identifying a functional bug, require request-changes. Add a self-consistency check to the pr-review synthesis step: if the summary text states findings should be addressed before merge, the verdict must be request-changes, not comment. Update comment-only criteria to clarify it applies only to stylistic, advisory, or process-related medium findings. Changes: - agents/review.md: Outcome section verdict criteria - skills/pr-review/SKILL.md: Step 6f verdict logic and self-consistency check Note: pre-commit could not run (shellcheck-py failed to install due to sandbox network restrictions). Secret scan passed. Closes #45
|
/fs-review |
|
🤖 Finished Review · ✅ Success · Started 8:54 PM UTC · Completed 9:09 PM UTC |
ReviewFindingsMedium
Low
Labels: PR fixes a review verdict bug and modifies protected agent/skill definitions |
| - `request-changes` — findings *requiring* resolution: one or more critical or | ||
| high findings; multiple medium-severity findings which could affect the | ||
| intended outcome of the PR | ||
| high findings; two or more medium-severity findings where at least one |
There was a problem hiding this comment.
[medium] logic-error
The new verdict criteria create a logical gap for exactly one medium finding that identifies a functional bug. The request-changes criterion requires two or more medium findings with at least one functional bug. The comment-only criterion explicitly excludes functional bugs. A single medium functional-bug finding satisfies neither condition, creating a contradiction. The same gap exists in skills/pr-review/SKILL.md at the parallel criteria.
Suggested fix: Add explicit handling for one medium functional-bug finding: either lower the request-changes threshold to include it, broaden comment-only to permit it, or add a dedicated bullet for this case. Apply the same fix to skills/pr-review/SKILL.md section 6f.
|
/fs-fix lower the request-changes threshold to include one functional-bug medium finding; update outdated language in "skills/code-review"; ignore all other findings |
|
🤖 Finished Fix · ✅ Success · Started 9:58 PM UTC · Completed 10:05 PM UTC |
…m finding - agents/review.md: request-changes now triggers on one or more medium findings identifying a functional bug (was: two or more) - skills/pr-review/SKILL.md: same threshold change in step 6f - skills/code-review/SKILL.md: update outdated verdict language to match new criteria (was still using old 'multiple medium findings which could affect the intended outcome' wording) Addresses review feedback on #49
🔧 Fix agent — iteration 1 (human-triggered)Addressed all 2 human-directed findings. Lowered the request-changes threshold from two-or-more to one-or-more functional-bug medium findings across agents/review.md and skills/pr-review/SKILL.md, and updated outdated verdict language in skills/code-review/SKILL.md to match. All other review findings ignored per human instruction. Fixed (3):
Tests: passed Updated by fullsend fix agent |
Replace the subjective "multiple medium-severity findings which could affect the intended outcome" criterion with an objective rule: two or more medium findings, at least one identifying a functional bug, require request-changes.
Add a self-consistency check to the pr-review synthesis step: if the summary text states findings should be addressed before merge, the verdict must be request-changes, not comment.
Update comment-only criteria to clarify it applies only to stylistic, advisory, or process-related medium findings.
Changes:
self-consistency check
Note: pre-commit could not run (shellcheck-py failed to install due to sandbox network restrictions). Secret scan passed.
Closes #45
Post-script verification
agent/45-fix-review-verdict-consistency)2540ede96537b32447321564bec60226efca120e..HEAD)