address-pr-feedback

This is a mutating workflow. You may edit files, rewrite commits, push branches, reply to comments, resolve threads, and hide eligible bot comments. Act immediately unless the user explicitly asks for a checkpoint.

All direct GitHub API, comment, review, and PR metadata operations must use the gh CLI. Do not use curl, direct API URLs outside gh api, or web fetching. When Graphite applies, gt may be used for stack-aware restacking and submission.

Prerequisites

• Run gh auth status. If authentication fails, stop and tell the user to run gh auth login.
• Record the authenticated GitHub login with gh api user --jq .login; use it to avoid duplicate replies from prior runs.
• Inspect the worktree with git status --short. Do not overwrite unrelated dirty changes. If unrelated dirty changes would block the work, stop and explain the conflict.
• Determine the current branch with git branch --show-current.

Find Target PRs

Use the PR URL, PR number, or branch the user supplied. If none was supplied, use the PR for the checked-out branch:

gh pr view --json number,title,url,baseRefName,headRefName,headRefOid,state,isCrossRepository,maintainerCanModify,headRepository,headRepositoryOwner