gh-issue-resolver
GitHub Issue Resolver
Overview
Implement and verify a fix for a GitHub Issue, starting from the agreed response plan that gh-issue-planner has already posted as a comment on the issue. This skill creates a feature branch, uses a git worktree as a temporary implementation sandbox, runs tests, opens a Pull Request, and verifies the fix against the original issue.
Prerequisites
- The target issue must have an agreed plan comment previously posted by
gh-issue-planner, identified by the HTML marker<!-- gh-issue-planner:agreed-plan -->near the end of the comment body. - If no such comment exists, stop and direct the user to run
gh-issue-plannerfirst. Do not improvise an unagreed plan in this skill.
Workflow
Step 1: Fetch the Issue and Agreed Plan
Run the following command (replace <id> with the issue number):
More from ymd38/dev-skills
spec-doc
>
13vulnerability-scan
>
12software-evaluation
>
9report-to-issues
|
4progress-dashboard
>
2gh-issue-planner
Fetch a GitHub Issue by ID using the gh CLI, investigate related code, propose a structured response plan (policy, impact scope, implementation steps), and post the agreed plan as a comment on the issue. Implementation/PR creation is out of scope — use gh-issue-resolver for that. Use when the user provides a GitHub Issue ID or asks to investigate/analyze/plan a GitHub Issue. Triggers include issue IDs like #42 or 'issue 42', requests such as Issueを調査して / Issueの対応方針を立てて, analyze issue #N, plan issue #N, investigate issue, look at issue.
1