solve

Included with Lifetime

$97 forever

Issue Blaster solve command: analyze GitHub issue numbers and generate 2-4 solution plans using gh, rg, and repo-local research.

General

What this skill does


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
$ARGUMENTS

## Instructions

### Step 1: Parse Arguments

Extract from $ARGUMENTS:
- Issue numbers (one or more integers)
- Optional `--repo owner/repo` flag

### Step 2: Detect Repository

If `--repo` not provided, detect it:
```bash
gh repo view --json nameWithOwner -q .nameWithOwner
```

### Step 3: Validate Issues

For each issue number, verify it exists:
```bash
gh issue view {number} --repo {repo} --json number
```

### Step 4: Solve Issues

#### Single Issue
If only one issue number is provided:
- Use the issue-blaster agent directly to analyze the issue
- The agent will create plans in `plans/issue-{N}/`

In Codex:
- Fetch issue details with `gh issue view {number} --repo {repo} --json number,title,body,comments,labels,assignees,url`
- Research the local codebase with `rg`, `git grep`, and targeted file reads
- Create `plans/issue-{N}/`
- Ensure `plans/` is ignored if writing plan files in the current repo
- Write 2-4 plan files using the format in `references/plan-format.md`
- Report the recommended option and plan file locations

#### Multiple Issues (Parallel)
If multiple issue numbers are provided, spawn parallel Task agents:

For EACH issue number, use the Task tool with:
- **subagent_type**: `"issue-blaster"`
- **run_in_background**: `true`
- **description**: `"Solving issue #{N}"`
- **prompt**: `"Analyze GitHub issue {repo}#{number}. The repository is {repo}."`

After spawning all tasks, wait for completion using TaskOutput.

In Codex:
- Process multiple issues sequentially by default
- Use Codex subagents only when the user explicitly asks for parallel agent work
- If subagents are authorized, assign one issue per subagent and keep write
  ownership disjoint by issue plan directory
- Aggregate each issue's JSON summary after all work completes

### Step 5: Report Results

Output a summary:

| Issue | Status | Plans Created | Location |
|-------|--------|---------------|----------|
| #{N}  | SUCCESS | {count} options | `plans/issue-{N}/` |

**Total**: {X}/{Y} issues solved successfully

### Step 6: Offer Follow-up

Offer to:
- Summarize the options for any issue
- Compare trade-offs between approaches
- Explain any option in detail

Files: 1

Size: 2.7 KB

Complexity: 10/100

Category: General

Source: https://github.com/grailautomation/claude-plugins/tree/main/issue-blaster/skills/solve

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts