address-code-review
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.
More from 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.
75marimo
Guide for creating and working with marimo notebooks, the reactive Python notebook that stores as pure .py files. This skill should be used when creating, editing, running, or deploying marimo notebooks.
51brainstorm
Guide for how to brainstorm an idea and turn it into a fully formed design.
41code-review
Guide for making code reviews. Use this when asked to make code reviews, or ask to use it before committing changes.
38bluesky
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.
37go
Guide for how to develop Go apps and modules/libraries. Always use this skill when reading or writing Go code.
37