Issue skill - Read the issue body and its comments in one call - #10553
Merged
Conversation
Step 1 told the agent to run "gh issue view <number> --comments". That view is not additive: the plain view prints the body and no comments, and --comments prints the comments and no body. A new report usually has no comments at all, so the command printed nothing and exited 0, which reads like a broken gh and sent the agent chasing --repo and shell variations that could not matter. Use the --json form instead, which always returns both, and say why so the next reader does not switch back. (do Get-DbaDatabase) Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Member
|
nice, thanks |
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.
Step 1 of the issue skill told the agent to read the issue with:
That view is not additive. The two forms are disjoint:
gh issue view 10549gh issue view 10549 --commentsgh issue view 10550 --commentsA fresh bug report normally has no comments yet, which is exactly when this skill runs.
ghthen prints nothing and exits 0. That looks like a brokenghrather than an empty comment list, and the natural reaction is to retry with--repo, then in another shell, then start ruling out pagers and encodings, none of which can matter. It cost a few minutes on #10550 before the--jsonfallback happened to work.The fix is the
--jsonform, which returns the body and the comments together in one call, plus a short note explaining the trap so nobody switches the command back:Verified against #10549 (has comments) and #10550 (has none). No command code is touched, so there is nothing for CI to test here.
馃 Generated with Claude Code