| name | issue-to-pr-resolver |
| description | Implement a GitHub issue end-to-end — create a worktree branch, implement the feature with tests, create a draft PR, then iteratively resolve all CI failures and review comments until the PR is clean. Use when you need to fully implement a GitHub issue from start to merge-ready. Triggers on "implement issue", "resolve issue", "/issue-to-pr-resolver <number>". |
| argument-hint | <issue-number> |
| allowed-tools | Bash, Read, Edit, Write, Glob, Grep, WebFetch, WebSearch |
Issue-to-PR Resolver
Implement GitHub issue #$ARGUMENTS in homeassistant-ai/ha-mcp end-to-end.
Phase 1: Setup
Read the issue:
gh issue view "$ARGUMENTS" --repo homeassistant-ai/ha-mcp --json title,body,labels,comments,author
Create a worktree from repo root:
cd "$(git rev-parse --show-toplevel)"
git checkout master && git pull origin master
git worktree add "worktree/issue-$ARGUMENTS" -b "feature/issue-$ARGUMENTS"
git -C "worktree/issue-$ARGUMENTS" submodule update --init --recursive
cd "worktree/issue-$ARGUMENTS"
Phase 2: Implement
- Analyze codebase structure and patterns before writing code
- Follow project conventions (see
AGENTS.md for patterns, naming, error handling)
- Write tests — all new MCP tools in
src/ha_mcp/tools/ need E2E tests
- Run tests locally:
cd tests && uv run pytest src/e2e/ -n2 --dist loadscope -v --tb=short
- Make atomic, well-described commits using conventional commit prefixes
Philosophy: Work autonomously. Don't ask about every small decision. Fix unrelated test failures encountered. Document all choices for the final summary.
If a non-obvious choice has significant consequences, present the available options to the user and let them choose.
Phase 3: Create PR
git push -u origin "feature/issue-$ARGUMENTS"
PR_NUMBER=$(gh pr create --draft \
--repo homeassistant-ai/ha-mcp \
--title "<descriptive title>" \
--body "Closes #$ARGUMENTS
## What does this PR do?
[description]
" | grep -oE '[0-9]+$')
Wait for CI:
gh pr checks "$PR_NUMBER" --repo homeassistant-ai/ha-mcp --watch
Before marking ready (gh pr ready), update the PR description to reflect all changes made.
Phase 4: Resolution Loop
Repeat until all checks green and no unresolved threads:
Check for issues:
gh pr checks "$PR_NUMBER" --repo homeassistant-ai/ha-mcp
gh api repos/homeassistant-ai/ha-mcp/pulls/"$PR_NUMBER"/comments \
--jq '.[] | {id, path, line, author: .user.login, body}'
gh api graphql -F pr="$PR_NUMBER" -f query='query($pr: Int!) { repository(owner:"homeassistant-ai", name:"ha-mcp") { pullRequest(number:$pr) { reviewThreads(first:100) { nodes { id isResolved comments(first:1) { nodes { databaseId body } } } } } } }'
Resolve each comment (both steps required):
gh api repos/homeassistant-ai/ha-mcp/pulls/"$PR_NUMBER"/comments/<COMMENT_ID>/replies \
-f body="✅ Fixed in [commit]. [explanation]"
gh api graphql -f query='mutation($threadId: ID!) { resolveReviewThread(input: {threadId: $threadId}) { thread { id isResolved } } }' \
-f threadId="<PRRT_...>"
After pushing fixes, wait and re-check:
gh pr checks "$PR_NUMBER" --repo homeassistant-ai/ha-mcp --watch
Phase 5: Final Report
Once all checks pass and all threads resolved:
gh pr comment "$PR_NUMBER" --repo homeassistant-ai/ha-mcp --body "## Implementation Summary
**Choices Made:**
- [key technical decisions with rationale]
**Problems Encountered:**
- [issues faced and how resolved]
- [unrelated test failures fixed, if any]
"
Report to user: PR number, status, key choices.
Rules
- Never commit to master — always work in the worktree
- Always create PRs as draft — never mark ready without user request
- Maximum 5 resolution iterations before reporting blockers
- Discovered improvements: fix-in-place by default. See AGENTS.md § Boy Scout Rule — Handling Discovered Improvements for the full rubric. Never open a follow-up PR or issue without explicit user approval; never populate
## Future improvements without the user explicitly confirming the work is out of scope.
