issue-blaster/skills/solve/SKILL.md
Issue Blaster solve command: analyze GitHub issue numbers and generate 2-4 solution plans using gh, rg, and repo-local research.
npx skillsauth add grailautomation/claude-plugins solveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Analyze the specified GitHub issue(s) and generate 2-4 solution plans. In
Claude Code this skill is normally invoked as /issue-blaster:solve. In Codex,
use the same workflow directly from the user's prompt; do not rely on Claude
Task or TaskOutput dispatch.
$ARGUMENTS
Extract from $ARGUMENTS:
--repo owner/repo flagIf --repo not provided, detect it:
gh repo view --json nameWithOwner -q .nameWithOwner
For each issue number, verify it exists:
gh issue view {number} --repo {repo} --json number
If only one issue number is provided:
plans/issue-{N}/In Codex:
gh issue view {number} --repo {repo} --json number,title,body,comments,labels,assignees,urlrg, git grep, and targeted file readsplans/issue-{N}/plans/ is ignored if writing plan files in the current reporeferences/plan-format.mdIf multiple issue numbers are provided, spawn parallel Task agents:
For EACH issue number, use the Task tool with:
"issue-blaster"true"Solving issue #{N}""Analyze GitHub issue {repo}#{number}. The repository is {repo}."After spawning all tasks, wait for completion using TaskOutput.
In Codex:
Output a summary:
| Issue | Status | Plans Created | Location |
|-------|--------|---------------|----------|
| #{N} | SUCCESS | {count} options | plans/issue-{N}/ |
Total: {X}/{Y} issues solved successfully
Offer to:
development
Parse and analyze Workato recipe JSON exports. Use when the user asks about a Workato recipe's logic, data flow, field mappings, error handling, or control flow. Also use when the user references a .recipe.json file or asks to debug a Workato integration.
databases
Review implementation plans as a staff software engineer. Use when the user asks for staff engineer feedback, senior engineering review, plan review, architecture review, implementation-plan critique, approval before proceeding, risk review, or feedback on a proposed technical plan.
tools
Use when the user invokes $spec-kit:tasks or /spec-kit:tasks, or asks to generate dependency-ordered tasks from the plan and repo context.
testing
Use when the user invokes $spec-kit:specify or /spec-kit:specify, or asks to create a brownfield-aware feature specification from a natural language description.