Starfie1d1272/dsh-github-skills / skills/gh-address-comments
gh-address-comments
VerifiedInspect or address GitHub pull request review feedback using thread-aware state. Use for requested changes, unresolved inline review threads, or review comments; fixing feedback authorizes local edits, not GitHub writes.
GitHub PR Review Feedback
Work through requested changes on a GitHub pull request using thread-aware review state.
Evidence
- Flat comments are not thread-aware review state (resolved/outdated/ inline-anchor semantics). Never collapse threads into flat comments.
- Use a visible structured-metadata capability when suitable; use a
thread-aware capability only if it genuinely preserves resolved/outdated/
inline-anchor semantics; otherwise use
scripts/fetch-review-threads.mjs. - Keep conversation comments, reviews, and review threads distinct.
- Incomplete or truncated evidence (
commentsTruncated) must be reported, never presented as a complete view.
Workflow
- Resolve the PR (given repo + number/URL, or current branch via local git context; ask if still ambiguous).
- Fetch the complete review context (see Evidence), then classify each thread: actionable, informational, already resolved/outdated, or ambiguous.
- Cluster actionable threads by file or behavior area; keep each change traceable to the thread or cluster it addresses.
- Decide intent. Analysis-only ("look at the review") gets analysis only. Address/fix intent ("address the review") authorizes local edits for unresolved actionable threads without mechanically re-asking.
- Surface conflicts, ambiguity, or regression risk before editing.
- Verify with the most relevant local checks for the touched area; never claim verification you did not run.
- Report addressed threads (file/line), intentionally unaddressed items and why, checks run, and remaining risk.
Remote write boundary
Local edits are not GitHub writes. Reply, resolve threads, submit a review,
push, or update the PR only on explicit user request or the host approval
boundary. If gh auth is missing or fails, report the blocker instead of
guessing.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |