respond-to-pr

# Respond to PR !`${CLAUDE_PLUGIN_ROOT}/bin/accelerator config context --skill respond-to-pr --fail-safe` **PR reviews directory**: !`${CLAUDE_PLUGIN_ROOT}/bin/accelerator config path review_prs --fail-safe` You are tasked with working through outstanding pull request review feedback in a systematic, interactive fashion. For each piece of feedback, you verify it against the codebase, confirm the approach with the user, make changes, and respond on GitHub. ## Initial Response When this command is invoked: 1. **Check if a PR number or URL was provided**: - If a PR number or URL was provided as an argument, identify the PR immediately - Begin the process 2. **If no argument provided**, respond with: ``` I'll help you respond to pull request review feedback. Please provide: 1. The PR number or URL (or I'll check the current branch) Tip: You can invoke this command with an argument: `/respond-to-pr 123` ``` Then check if the current branch has a PR: `gh pr view --json number,url,title,state 2>/dev/null` If a PR is found on the current branch, offer to use it. If not, wait for the user's input. ## Process Steps ### Step 1: Fetch PR Context and Outstanding Feedback 1. **Get PR metadata**: ```bash gh pr view {number} --json number,url,title,state,baseRefName,headRefName ``` 2. **Validate PR state**: Check that `state` is `OPEN`. If the PR is closed or merged, inform the user and use the `AskUserQuestion` tool with two options: 1. **Yes, proceed a...