feat: add guidance for fetching all GitHub PR comment types (issue #701)#1729
Open
ElizioMartins wants to merge 1 commit into
Open
feat: add guidance for fetching all GitHub PR comment types (issue #701)#1729ElizioMartins wants to merge 1 commit into
ElizioMartins wants to merge 1 commit into
Conversation
…ra#701) Add 'Fetching GitHub PR Feedback' section to receiving-code-review skill with explicit commands for all three comment types: 1. Inline review comments (line-specific): gh api repos/{owner}/{repo}/pulls/{pr}/comments 2. Review bodies (summary + nitpicks): gh api repos/{owner}/{repo}/pulls/{pr}/reviews 3. Direct PR comments (top-level): gh api repos/{owner}/{repo}/issues/{pr}/comments Warns against relying solely on 'gh pr view' or inline comments endpoint which miss review bodies and top-level comments.
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.
Who is submitting this PR?
What problem are you trying to solve?
Issue #701: The
receiving-code-reviewskill's step 1 ("READ: Complete feedback without reacting") doesn't specify how to fetch all feedback. In practice, agents usingghCLI may only fetch inline review comments and miss other comment types that often contain the most significant feedback.What does this PR change?
Adds a new "Fetching GitHub PR Feedback" section to the skill with explicit commands for all three GitHub PR comment types:
gh api repos/{owner}/{repo}/pulls/{pr}/commentsgh api repos/{owner}/{repo}/pulls/{pr}/reviewsgh api repos/{owner}/{repo}/issues/{pr}/commentsIncludes warning against relying solely on
gh pr viewor inline comments endpoint.Is this change appropriate for the core library?
Yes - this affects all users receiving code review feedback via GitHub PRs, regardless of project domain.
What alternatives did you consider?
Alternative would be to auto-fetch in a script, but the skill should teach the agent the correct commands to use.
Does this PR contain multiple unrelated changes?
No - single cohesive addition to the skill.
Existing PRs
Environment tested
Evaluation
Rigor
Human review