← ClaudeAtlas

gh-issue-resolverlisted

Implement and verify a fix for a GitHub Issue whose response plan has already been posted as a comment by gh-issue-planner. Creates a feature branch, applies the agreed plan, runs tests, and opens a Pull Request. Use when the user asks to implement/fix/resolve a planned GitHub Issue. Triggers include requests such as Issueを実装して / Issueを修正して / Issueを対応して, implement issue #N, fix issue #N, resolve issue #N, work on issue #N. Prerequisite: an agreed plan comment must exist on the issue (run gh-issue-planner first if not).
northraystudio/maruda · ★ 4 · AI & Automation · score 75
Install: claude install-skill northraystudio/maruda
# 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-planner` first**. 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): ```bash gh issue view <id> --json number,title,body,labels,state,url,comments ``` From the `comments` array: 1. Locate the most recent comment whose body contains the marker `<!-- gh-issue-planner:agreed-plan -->`. 2. Treat that comment as the **agreed plan** and extract the 対応方針 / 影響範囲 / 実装方法 sections. 3. If no such comment exists, abort with a message asking the user to run `gh-issue-planner` first. ### Step 2: Branch and Worktree Setup Resolve `<base-ref>` first — everything downstream (the branch, the PR's base, and the verification baseline in Step 8) is measured against it: | Flow | `<base-ref>` | |------|--------------| |