Respond to code review

Work from the actual review comments and current code. Verify claims before changing code or replying.

Scope

• If the user asks only to check or summarize comments, collect and assess them, then report findings. Do not edit code or post replies.
• If the user asks to address or respond to comments, apply verified fixes, run relevant checks, and reply as authorized.
• Identify the pull request or merge request from the link, number, current branch, or repository context. Ask only if more than one target remains plausible.
• Use the team's existing authenticated tools. If GitHub CLI is missing and would help, read the optional one-time setup guide; offer it to the user rather than assuming they want it installed.

Workflow

Required on every use: Identify the review platform and read its procedure before collecting feedback: GitHub, GitLab, or Bitbucket. Read the matching reference even if you have used this skill before; it contains the platform's collection, reply, and resolution steps. Skip the other platforms' references; read a one-time setup guide only when setup is needed.