solve-issuelisted

Solve the GitHub issue at `$ISSUE_URL` and create a pull request. ## Context - **Your GitHub Username**: `$GITHUB_USERNAME` (from global CLAUDE.md or prompt) - **Current Workspace**: This is your fork of the original repository - **Remote Origin**: Set to `$GITHUB_USERNAME/[original-repo-name]` - **Target**: All commits/pushes go to your fork, PR opens to original repository ## GitHub Tools - **GitHub MCP**: Preferred for collaboration (PRs, issues, comments, reviews). Tool names follow `mcp__github__*`. - **gh CLI**: Fallback when MCP unavailable - `gh --help` for commands - Check auth: `gh auth status` ## Steps 1. **Fetch Issue Details** (GitHub MCP): - Get issue description, labels, comments - Understand the problem completely 2. **Examine Repository and Code Patterns**: - Find and read relevant files - **Study recently merged PRs** (last 3-6 months) to understand: * Code style and patterns preferred by maintainers * Naming conventions and structure * Test approaches and coverage patterns * Comment style and documentation preferences - Reference similar working implementations - Read CONTRIBUTING.md if exists, follow rules - **Adapt your code style to match the project's existing patterns** 3. **Create Solution Plan** and get approval BEFORE implementing: - Which files will change (with line numbers) - Expected behavior difference (before/after) 4. **Implement Changes** (after approval): - Make small, focused changes