aea-report-finalize: front-load aea-parse-tags check to Step 0 - #94
Open
larsvilhuber wants to merge 1 commit into
Open
larsvilhuber wants to merge 1 commit into
larsvilhuber wants to merge 1 commit into
Conversation
Several finishing-pass runs went looking for the retired aeareq script and stalled/asked the user instead of using aea-parse-tags, even though Step 4 already names it correctly. Add an explicit tool-presence check and a "don't substitute a different tool name" note to Step 0, so the agent hits this before it's had a chance to act on stale assumptions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
aea-report-finalizefinishing-pass runs (6/6 in one batch, aearep-9134/9135/9145/9222/9488/9749) went looking for the retiredaeareqscript during Step 4, found it missing, and stopped to ask the human editor — even though Step 4 already correctly namesaea-parse-tagsas the current tool.aea-parse-tags, with a "formerlyaeareq" note) — the failure was that agents acted on stale assumptions before reading that far into the file.command -v aea-parse-tagscheck to Step 0, right where the repo is first located, plus an explicit note not to substitute a different/older tool name if it's missing — so the agent hits the current tool name before it has a chance to go hunting on its own.Test plan
aea-report-finalizeagainst a repo whereaea-parse-tagsis installed and confirm Step 0 output includes its path, no behavior change downstream.aea-parse-tagsis absent and confirm the skill stops at Step 0 with a clear message, instead of discovering the gap later at Step 4.🤖 Generated with Claude Code