AntFleet

Disagreement · 3cf9137d-anthropic-1

Var parsing rule for 'dry-run' prefix is ambiguous when var equals exactly 'dry-run'

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

Opus finding

Var parsing rule for 'dry-run' prefix is ambiguous when var equals exactly 'dry-run'

lowapi-contractmedium
  • skills/fork-first-run-alert/SKILL.md:71-75
The regex ^dry-run will also match strings like 'dry-runs' or 'dry-run-foo' with no separator. The spec does not state what separator (space? colon?) splits the dry-run prefix from the owner/repo remainder. Examples elsewhere in aeon.yml use 'dry-run' alone or 'owner/repo' alone but never combined. If a caller passes 'dry-run aaronjmars/aeon', the remainder after stripping is ' aaronjmars/aeon' (leading space) which fails the owner/repo regex and results in FORK_FIRST_RUN_ALERT_BAD_VAR even though the intent is clear.

Recommendation

Specify the separator explicitly (e.g., 'dry-run' or 'dry-run <owner/repo>' with whitespace trim) and that the remainder is trimmed before regex match.

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 →