AntFleet

Disagreement · 9bb17981-anthropic-1

OUT-OF-SCOPE closing path posts a comment via gh pr close --comment in addition to step 6's triage comment, producing duplicate comments

solo Opus
repo 6f7fc663·PR #7·reviewed 1 week ago

Opus finding

OUT-OF-SCOPE closing path posts a comment via gh pr close --comment in addition to step 6's triage comment, producing duplicate comments

lowbughigh
  • skills/pr-triage/SKILL.md:130-138
  • skills/pr-triage/SKILL.md:149-156
Step 6 already posts the `**Triage:** OUT-OF-SCOPE …` comment. Step 8 then issues `gh pr close --comment "Closed as out-of-scope …"`, which posts a second comment on the same PR in the same run. This violates the 'one triage comment per PR per run' constraint and clutters the PR. Also, the second comment does not start with `**Triage:**`, so it won't be picked up by the dedup check next run — minor but noteworthy.

Recommendation

Either drop `--comment` from `gh pr close` (the triage comment already explains everything) or fold the close message into the triage comment and skip step 6 for OUT-OF-SCOPE.

Other reviewer

The other reviewer flagged nothing in this file/line range.

Why this didn't post

This finding didn't meet AntFleet's unanimous agreement threshold. Both frontier models review every PR independently; only findings they both flag with the same severity and category are posted to the PR. This one fell through.

read the methodology →