Component
Documentation
Problem & Motivation
The pr-review skill had no guidance on how to post follow-up replies to existing review threads. In practice, posting individual replies via pulls/comments/{id}/replies before submitting the main review creates a separate ghost review object per reply on GitHub, polluting the review history.
Additionally, the in_reply_to example only had a PowerShell variant, making the skill inconsistent with the rest of the file which covers both Windows and Linux/macOS.
Proposed Solution
Add a clearly-labelled warning block in Step 5 Branch B of the skill:
- Forbid posting individual thread replies before the main review
- Document how to bundle replies into the single POST /reviews call using the in_reply_to field
- Provide both PowerShell and bash variants
Bump skill version to 1.2.0.
Example
n/a - documentation-only change
Agent Context (optional)
agent_name: GitHub Copilot
llm: Claude Sonnet 4.6
tool: VS Code Chat
confidence: high
source_event: ghost reviews observed during PR #395 review session
discovery_method: runtime_observation
Component
Documentation
Problem & Motivation
The pr-review skill had no guidance on how to post follow-up replies to existing review threads. In practice, posting individual replies via
pulls/comments/{id}/repliesbefore submitting the main review creates a separate ghost review object per reply on GitHub, polluting the review history.Additionally, the in_reply_to example only had a PowerShell variant, making the skill inconsistent with the rest of the file which covers both Windows and Linux/macOS.
Proposed Solution
Add a clearly-labelled warning block in Step 5 Branch B of the skill:
Bump skill version to 1.2.0.
Example
n/a - documentation-only change
Agent Context (optional)
agent_name: GitHub Copilot
llm: Claude Sonnet 4.6
tool: VS Code Chat
confidence: high
source_event: ghost reviews observed during PR #395 review session
discovery_method: runtime_observation