issue-ingest

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

1|Updated May 17, 2026

Search Tags:#github #issue management #codebase analysis #specification generation #resolution planning

Ready to run

npx skills add https://github.com/djimit/djimitflo --skill issue-ingest-djimit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-ingest
Source: https://github.com/djimit/djimitflo/tree/main/.opencode/skills/issue-ingest
Command: npx skills add https://github.com/djimit/djimitflo --skill issue-ingest-djimit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the intake, localization, and specification generation for GitHub issues, streamlining the process from problem identification to resolution planning.

Core Features & Use Cases

GitHub Issue Intake: Handles the intake of GitHub issues with support for URL-based activation and protocol-driven processing.
Root Cause Localization: Utilizes active swarm agents to scan codebases and identify potential root causes.
Spec Generation: Produces resolution specifications that can be used for further planning or tracing.
Transition Management: Offers seamless transition to planning or tracing based on input flags.

Quick Start

Activate the issue-ingest skill with the command: /swarm issue <issue-url>

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 intake and generate a resolution specification?▼

Automating GitHub issue intake involves activating a protocol-driven process via URL that scans the codebase to localize root causes and produces a structured resolution specification. You can trigger this workflow directly using the command `/swarm issue <issue-url>`.

How does root cause localization work for GitHub issues in a codebase?▼

Root cause localization for GitHub issues works by deploying active swarm agents to scan the repository codebase. These agents analyze the codebase context around the issue to identify potential root causes and automatically generate a resolution specification for further planning.

Can I transition directly from issue intake to planning and tracing workflows?▼

Yes, you can transition directly from issue intake to planning or tracing workflows. The process supports seamless transition management based on input flags, allowing the generated resolution specifications to feed immediately into downstream planning or tracing protocols.

Do I need to manually configure dependencies to scan codebases for GitHub issue resolution?▼

No manual dependency configuration is required to scan codebases for GitHub issue resolution. The skill operates with no external dependencies, utilizing built-in scripts and references to execute protocol-driven processing and swarm agent root cause identification autonomously.

What is the best way to streamline GitHub issue resolution protocols for codebase analysis?▼

The best way to streamline GitHub issue resolution protocols is using URL-based activation to trigger automated intake. Swarm agents scan the codebase to identify root causes and generate resolution specifications, replacing manual issue analysis with a protocol-driven workflow.