AntFleet

Disagreement · 3c2fcd11-openai-2

Inconsistent BAD_VAR behavior: spec says “exit without notifying” but log template fixes Notification: sent

solo GPT-5
repo 6f7fc663·PR #9·reviewed 1 week ago

GPT-5 finding

Inconsistent BAD_VAR behavior: spec says “exit without notifying” but log template fixes Notification: sent

lowdocs-gaphigh
  • skills/show-hn-draft/SKILL.md
  • skills/show-hn-draft/SKILL.md
Step 1 instructs to exit without notifying on a bad var, but the Step 9 log template hardcodes “Notification: sent.” Implementers following the template verbatim could write misleading logs. The spec should make the notification line conditional.

Recommendation

Amend Step 9 to set the notification line conditionally, e.g., “Notification: sent | skipped,” and explicitly state that on SHOW_HN_DRAFT_BAD_VAR no notification is sent and no draft file is written.

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 →

From the same review

These findings passed the unanimous gate on the same PR review. The disagreement above was filtered out; the findings below were posted.

← back to all disagreementsview public receiptssee unanimous findings + anatomies →
Tweet ↗