AntFleet · Documented 80-fork cap and pushed_at sorting not reflected in fallback snippet (risk of budget overrun or inconsistent order)

GPT-5 finding

Documented 80-fork cap and pushed_at sorting not reflected in fallback snippet (risk of budget overrun or inconsistent order)

lowdocs-gaphigh

skills/fork-first-run-alert/SKILL.md:124-131
skills/fork-first-run-alert/SKILL.md:267
skills/fork-first-run-alert/SKILL.md:118-122

The text promises a hard 80-fork cap and sorting by pushed_at desc, but the provided command neither sorts nor trims to 80. This inconsistency can lead to scanning more forks than intended and unpredictable ordering for trimming decisions.

Recommendation

Amend the snippet to explicitly sort and cap: after collecting forks, apply jq 'sort_by(.pushed_at) | reverse | .[:80]' before iterating. Also note logging 'truncated_at=80' when applied.

Documented 80-fork cap and pushed_at sorting not reflected in fallback snippet (risk of budget overrun or inconsistent order)

Documented 80-fork cap and pushed_at sorting not reflected in fallback snippet (risk of budget overrun or inconsistent order)

Why this didn't post