ReddRadar
Agent skill
address-code-review
Address code review feedback by walking through comments one at a time with the user. Use when the user has received code review comments — on a GitHub PR, in a document in the repo, or directly in conversation — and wants to work through them methodically. Also trigger when the user mentions "address review", "review comments", "PR feedback", or wants to respond to code review feedback.
Install this agent skill to your Project
npx add-skill https://github.com/maragudk/skills/tree/main/address-code-review
SKILL.md
Address Code Review
Work through code review comments with the user, one comment at a time. Never present multiple comments at once.
Input sources
Comments may come from:
- GitHub PR - Fetch inline and general comments using
gh api - Document in the repo - Parse whatever markdown structure is found
- Conversation - Comments given directly by the user
Process
1. Collect feedback
- GitHub PR: Use GraphQL to fetch all comments in one go. Fetch inline review comments via
pullRequest.reviewThreadsand general PR comments viapullRequest.comments. Skip already-resolved threads (isResolved). Still present outdated but unresolved comments (isOutdated), noting to the user that the code has changed since the comment was left. - Document: Read the file and extract review items.
- Conversation: Use the comments as provided.
2. Triage one at a time
For each comment, strictly one at a time:
- Present the comment to the user.
- Share your own assessment: agree, disagree, or propose an alternative. Explain your reasoning briefly.
- Wait for the user to decide what to do (apply, skip, modify, etc.).
- Record the agreed-upon action. Do not apply code changes yet.
For GitHub PR inline comments: immediately reply to the comment on GitHub and resolve the thread after discussion.
3. Apply changes
After all comments have been discussed, apply all agreed-upon code changes in one batch.
For GitHub PR general comments (which may contain multiple issues in one comment): post a single summary reply after all issues in that comment are addressed.
For document sources: update the document with status/progress as appropriate.
GitHub CLI reference
| Action | Command |
|---|---|
| Fetch all comments | GraphQL query on pullRequest.reviewThreads (inline) and pullRequest.comments (general) |
| Reply to inline comment | gh api repos/{owner}/{repo}/pulls/{pr}/comments/{id}/replies -X POST -f body="..." |
| Reply to general comment | gh api repos/{owner}/{repo}/issues/{pr}/comments -X POST -f body="..." |
| Resolve a thread | GraphQL mutation resolveReviewThread(input: {threadId: "..."}) |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
maragudk/skills
bluesky
Guide for posting content to the Bluesky social network using the bsky terminal app. This skill should be used proactively when working in public repositories and there is interesting, shareable content (new features, insights, achievements, or announcements worth sharing with the community). Use it when asked to post to Bluesky, or when content seems worth sharing publicly.
maragudk/skills
observable-plot
maragudk/skills
datastar
Guide for building interactive web UIs with Datastar and gomponents-datastar. Use this skill when adding frontend interactivity to Go web applications with Datastar attributes.
maragudk/skills
go
Guide for how to develop Go apps and modules/libraries. Always use this skill when reading or writing Go code.
maragudk/skills
worktrees
Guide for using git worktrees to parallelize development with coding agents. Use this skill when the user requests to work in a new worktree or wants to work on a separate feature in isolation (e.g., "Work in a new worktree", "Create a worktree for feature X").
maragudk/skills
collaboration
Guide for collaborating on GitHub projects. This skill should be used when contributing to projects, creating PRs, reviewing code, or managing issues on GitHub.
Didn't find tool you were looking for?