AntFleet

Disagreement · 32b75da9-openai-3

Inconsistent field name between captured run metadata ('name') and template fallback ('workflow_name')

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

GPT-5 finding

Inconsistent field name between captured run metadata ('name') and template fallback ('workflow_name')

lowdocs-gaphigh
  • skills/fork-first-run-alert/SKILL.md:149-152
  • skills/fork-first-run-alert/SKILL.md:154-156
  • skills/fork-first-run-alert/SKILL.md:182-184
The jq selection captures the field as 'name', but later documentation and templates refer to 'workflow_name'. This mismatch can lead to empty fallback values in notifications if implementers follow the template literally.

Recommendation

Standardize on 'name' throughout, or explicitly rename during capture: '{workflow_name: .name, display_title, updated_at, html_url}'. Update the template and state schema references accordingly.

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 →