skills.rest
ZaxbyHub
ZaxbyHubOFFICIAL
Explore all skills by this author →
GitHub

issue-ingest

Parse GitHub issue URLs into resolution specs with root cause hypotheses.

437|45|Updated Jan 27, 2026
Search Tags:#triage#workflow-automation#root-cause-analysis#spec-generation#github-issue#bug-resolution#code-localization
One-click install
npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill issue-ingest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-ingest
Source: https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/issue-ingest
Command: npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill issue-ingest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually processing GitHub issues—triage, root cause identification, and spec writing—is slow, inconsistent, and often leads to misaligned fixes that waste engineering time and delay delivery.

Core Features & Use Cases

  • Structured Issue Intake: Automatically parses GitHub issue URLs into normalized intake notes with observed behavior, expected behavior, reproduction steps, and environment context, flagging missing information as needed.
  • Confidence-Scored Root Cause Localization: Generates falsifiable root cause hypotheses, validates top candidates via specialized codebase agents, and prunes to a single high-confidence root cause.
  • Testable Spec Generation: Produces standards-aligned resolution specs with requirement numbering, Given/When/Then scenarios, built-in clarification funnels, and optional QA gate selection, with automatic transitions to planning or full fix workflows when requested.
  • Use Case: A developer receives a bug report GitHub issue; running this skill automatically fetches the issue, identifies the responsible code area, generates a testable fix spec, and moves directly to implementation planning if the plan=true flag is set.

Quick Start

Use the issue-ingest skill to process the GitHub issue at https://github.com/your-org/your-repo/issues/456 and generate a resolution spec with root cause analysis and optional transition to planning.

Frequently Asked Questions about issue-ingest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issue triage and root cause analysis?▼

Automating GitHub issue triage involves parsing issue URLs into normalized intake notes, generating falsifiable root cause hypotheses, and validating candidates to isolate a high-confidence root cause.

How do I generate testable resolution specs from bug reports?▼

Generating testable resolution specs from bug reports produces standards-aligned documents with requirement numbering, Given/When/Then scenarios, and built-in clarification funnels to reduce fix misalignment.

What is the best way to localize code responsible for a GitHub bug?▼

The best way to localize code responsible for a GitHub bug is applying specialized codebase agents to validate top root cause candidates, pruning hypotheses until a single high-confidence area is identified.

Can I transition directly from issue intake to implementation planning?▼

Yes, you can transition directly from issue intake to implementation planning by setting optional flags, moving from generated resolution specs into full fix-and-PR workflows without manual handoff.

Does issue triage work with feature requests and task tickets?▼

Yes, issue triage works with feature requests and task tickets ingested via GitHub issue URLs, standardizing the intake process across bug reports and non-bug development tasks.

Why does manual issue resolution often lead to misaligned fixes?▼

Manual issue resolution leads to misaligned fixes because triage, root cause identification, and spec writing are slow and inconsistent, lacking standardized testable resolution specs gated by QA selection.

Related Skills

Explore More Software Engineering Skills→
mediar-aimediar-ai
1.6k

Terminator Issue Reporter

Generate structured GitHub issues for Terminator failures with logs and reproduction steps.

Official
Advanced
bponghnengbponghneng

review-spec

Generate structured specification documents from GitHub PR review comments.

Community
Intermediate
Covcloud-LLCCovcloud-LLC

diagnose

Reproduce failure paths and trace execution to identify root causes.

Official
Advanced
djimitdjimit
1

issue-ingest

Automate GitHub issue intake, root cause localization, and resolution specification generation.

Community
Advanced