PR Fix: /pr-fix command makes the agent fix a failing PR

Runs the same job in your agent session, on the plan you are signed in with. No API key, no Action.

Do the job of the "PR Fix: /pr-fix command makes the agent fix a failing PR" workflow from AgentFlows (https://agentflows.sh/flows/agentics-pr-fix) right here, in this session, using the plan I'm signed in with. No API key and no GitHub Action.

Install these agent skills first. Download each SKILL.md from its source (respect its license) into .claude/skills/<name>/SKILL.md, or wherever this agent loads skills from:
- Debug: https://github.com/anthropics/knowledge-work-plugins/blob/main/engineering/skills/debug/SKILL.md (Apache-2.0), notes at https://agentflows.sh/skills/debug
- Iterate on a PR until CI passes and review feedback is addressed: https://github.com/getsentry/skills/tree/main/skills/iterate-pr (Apache-2.0), notes at https://agentflows.sh/skills/getsentry-iterate-pr

What it does: Comment /pr-fix on a pull request and the agent looks at the failing checks, finds the root cause, and pushes a fix to the PR branch.

The workflow normally runs on: slash_command: /pr-fix comment. Instead, ask me which pull request, issue, or branch to work on, then follow these instructions:

```text
# PR Fix

You are an AI assistant specialized in fixing pull requests with failing CI checks. Your job is to analyze the failure logs, identify the root cause of the failure, and push a fix to the pull request branch for pull request #${{ github.event.issue.number }} in the repository ${{ github.repository }}.

1. Read the pull request and the comments

2. Take heed of these instructions: "${{ steps.sanitized.outputs.text }}"

  - (If there are no particular instructions there, your instructions are to fix the PR based on CI failures. You will need to analyze the failure logs from any failing workflow run associated with the pull request. Identify the specific error messages and any relevant context that can help diagnose the issue.  Based on your analysis, determine the root cause of the failure. This may involve researching error messages, looking up documentation, or consulting online resources.)

3. Check out the branch for pull request #${{ github.event.issue.number }} and set up the development environment as needed.

4. Formulate a plan to follow the instructions. This may involve modifying code, updating dependencies, changing configuration files, or other actions.

5. Implement the changes needed to follow the instructions.

6. Run any necessary tests or checks to verify that your fix follows the instructions and does not introduce new problems.

7. Run any code formatters or linters used in the repo to ensure your changes adhere to the project's coding standards and fix any new issues they identify.

8. If you're confident you've made progress, push the changes to the pull request branch.

9. Add a comment to the pull request summarizing the changes you made and the reason for the fix.
```

Use the gh CLI for anything on GitHub, and show me what you plan to post or change before you do it.