메뉴
Address review comments (including Copilot comments) on the active pull request. Use when: responding to PR feedback, fixing review comments, resolving PR threads, implementing requested changes from reviewers, addressing code review, fixing PR issues.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | address-pr-comments |
| description | Address review comments (including Copilot comments) on the active pull request. Use when: responding to PR feedback, fixing review comments, resolving PR threads, implementing requested changes from reviewers, addressing code review, fixing PR issues. |
Work through open review threads on the current PR and fix the issues raised. Do not post replies or resolve threads — produce a summary the user can use to respond manually.
Follow the read-pr skill (no argument — it resolves the open PR for the current branch). This fetches the PR details, diff, and review threads with their resolved/unresolved state.
From the threads read-pr returned, work only the unresolved ones. For each, note:
Work through every open thread:
Do not post any GitHub comments or resolve any threads.
After all fixes are applied, output a checklist the user can use when responding to reviewers:
## PR comment summary
**Fixed in code:**
- [ ] `src/foo.ts:42` — @reviewer: "use const here" → changed `let` to `const`
- [ ] `src/bar.ts:17` — @reviewer: "missing null check" → added early return
**Needs your response (question / context):**
- [ ] `src/baz.ts:88` — @reviewer: "why not use X here?" → explain your reasoning
**Won't fix / out of scope:**
- [ ] `src/qux.ts:5` — @reviewer: "rename this file" → outside this PR's scope, consider responding to defer
This gives the user everything needed to go reply to threads and resolve them manually.
Remind the user to:
/ship when the PR is ready to push the fixesScaffold a web repo with pnpm, Astro, and astro-bulma — plus Drizzle when the site needs a database — including package.json scripts for build/lint/test/fmt (and db:migrate when db-backed). Use when: setting up a new Astro project, scaffolding a web repo, initializing the standard web stack. Building block for create-website.
Add a GitHub Actions CI workflow running build, lint, test, and fmt checks with pnpm. Use when: adding CI, setting up GitHub Actions checks, adding a build/lint/test workflow. Building block for create-website.
Create a new website end-to-end: Astro repo with pnpm/astro-bulma; GitHub Pages for static sites, or Turso + Fly.io when the site needs a database; GitHub Actions for CI and deploy. Use when: creating a new website, spinning up a new web project, new site, scaffolding a static or full-stack Astro project.
Create a new app on Fly.io for the current project without deploying it, generating fly.toml and a Dockerfile. Use when: creating a Fly.io app, setting up Fly hosting, fly launch. Building block for create-website.
Add a GitHub Actions workflow that builds a static site and deploys it to GitHub Pages, with an optional custom domain. Use when: deploying a static site, GitHub Pages hosting, static site with a custom domain. Building block for create-website.
Add a GitHub Actions workflow that deploys to Fly.io on merge to main, with db migrations run as a Fly release_command. Use when: adding a deploy workflow, deploying on merge, setting up continuous deployment to Fly.io. Building block for create-website.