Repository navigation
Say that jq is optional (for discussion) - #58
Open
anakanemison wants to merge 1 commit into
Open
anakanemison wants to merge 1 commit into
anakanemison wants to merge 1 commit into
Conversation
SKILL.md lists jq among the tools every migration requires, and says to stop and ask the user to install anything missing. No script in scripts/ calls jq. An unattended agent cannot ask, so it improvises. In any2bazel-lab's migration runs, in containers without jq, agents tried `sudo apt-get install jq`, downloaded a jq binary from GitHub (two runs), or spent three or four calls establishing they did not need it. One agent wrote the finding down itself: "No script under the skill's scripts/ directory invokes it". jq is now described as a convenience, with python3 -m json.tool as the fallback. In the lab's six runs with this change, no agent installed or downloaded jq. This is a proposal for discussion: the maintainers may want jq for interactive use, where asking the user is cheap. Lab-Proposal: P28 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
I added this preemptively since I was going to add template I suggest removing |
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
2 participants
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.
Part 23 of 23 of a stacked series (tracking issue: #35). Based on
D5-transitive-defines, the previous part: review and merge that first.Kind: discussion. Lab proposal: P28.
What the migration runs showed
No script uses jq, but the prerequisites require it and say to stop and ask. Every agent in the lab's first ten runs with this series spent calls on it, and two downloaded a binary from GitHub. With this, no agent installed it (runs 091-096).
The change
SKILL.md lists jq among the tools every migration requires, and says to stop
and ask the user to install anything missing. No script in scripts/ calls
jq. An unattended agent cannot ask, so it improvises. In any2bazel-lab's
migration runs, in containers without jq, agents tried
sudo apt-get install jq, downloaded a jq binary from GitHub (two runs), orspent three or four calls establishing they did not need it. One agent wrote
the finding down itself: "No script under the skill's scripts/ directory
invokes it".
jq is now described as a convenience, with python3 -m json.tool as the
fallback. In the lab's six runs with this change, no agent installed or
downloaded jq.
This is a proposal for discussion: the maintainers may want jq for
interactive use, where asking the user is cheap.
Testing
pytest tests/at this commit: 196 passed (130 onmain).🤖 Generated with Claude Code