AntFleet

Disagreement · 89395cd4-anthropic-3

PARENT_REPO referenced but never defined

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

Opus finding

PARENT_REPO referenced but never defined

lowbughigh
  • skills/contributor-spotlight/SKILL.md:144-146
`${PARENT_REPO}` is referenced as the comparison baseline but is never defined in the skill. It cannot be inferred from `FEATURED_FORK` (a fork knows its parent only via the GitHub API). The implementer has to guess — and a wrong guess (e.g. assuming AntFleet/aeon-bench when the fork was forked from a different upstream) silently inverts OPERATOR_AUTHORED labeling: skills the operator actually imported from upstream get falsely marked with ★ as "operator-authored."

Recommendation

Either hardcode the canonical parent (`AntFleet/aeon-bench`) with a comment, or derive it from `gh api repos/${FEATURED_FORK} --jq .parent.full_name` (which is already a free byproduct of Step 4 if you ask for `.parent`).

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 ↗