fix-issues

# PR Comment Fixer

Automatically processes GitHub pull request review comments and applies code fixes to address reviewer feedback.

## Workflow

Follow this workflow when the user requests PR comment fixes:

### 1. Extract PR Information

Parse the PR number from the user's request. Accept formats like:
- "PR #1234"
- "pull request 1234"
- "#1234"
- Just the number "1234"

### 2. Fetch PR Details

Use GitHub CLI to get PR information:

```bash
gh pr view <PR_NUMBER> --json number,title,headRefName,repository
```

Extract:
- `headRefName`: The PR branch name
- `repository`: Owner and repo name

### 3. Ensure Repository Access

Check if running locally or remotely:

```bash
git rev-parse --git-dir 2>/dev/null
```

If this fails (not in a git repository):
- Clone the repository: `gh repo clone <OWNER>/<REPO>`
- Change to repository directory

If successful (already in repository):
- Verify it's the correct repository
- Continue with existing local clone

### 4. Checkout PR Branch

Switch to the PR branch:

```bash
git fetch origin
git checkout <BRANCH_NAME>
git pull origin <BRANCH_NAME>
```

### 5. Fetch All PR Comments

Retrieve review comments using GitHub CLI:

```bash
gh pr view <PR_NUMBER> --json reviews,comments --jq '.reviews[].comments[], .comments[]'
```

Parse the JSON output to extract:
- Comment body/text
- File path (if applicable)
- Line number or diff position
- Author
- Whether it's resolved or pending

### 6. Evaluate Comment Relevance

For each comment, determine if it's actionable:

**Actionable comments** (should be fixed):
- Requests for code changes (naming, formatting, refactoring)
- Bug reports or logic errors
- Suggestions for improvements
- Security or performance concerns
- Missing error handling
- Code quality issues

**Non-actionable comments** (skip):
- General discussion or questions already answered
- Comments marked as resolved
- Informational comments with no change request
- Compliments or approvals

When in doubt, err on the side o