issue

Capture issue context and route it to memory, egregore-core, or GitHub.

275|17|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/egregore-labs/egregore --skill issue-egregore-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/egregore-labs/egregore/tree/main/.claude/skills/issue
Command: npx skills add https://github.com/egregore-labs/egregore --skill issue-egregore-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When teams encounter bugs, feature gaps, or workflow blockers, this Skill captures the context and routes the issue to the appropriate destination (memory graph, egregore-core, or a specific repository) for timely triage and resolution.

Core Features & Use Cases

  • Capture: Create a structured issue snapshot that preserves context, environment, and recent activity.
  • Smart routing: Determine whether to store the issue in memory, file it on egregore-core, or file a GitHub issue, based on content signals and user input.
  • Triage & tracking: Generate a human-tractable record in memory and optionally notify teams or file GitHub issues for visibility.
  • Use Case: A team member reports a flaky deployment that affects multiple services; the Skill captures the report and routes it to the correct owner or repo for action.

Quick Start

Explain a new issue by describing the problem and what outcome you want; the system will guide you through capture, routing, and storage.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I automatically route issue triage to GitHub or memory?

Automated issue routing captures context and directs it to memory, upstream, or GitHub based on content signals. The system analyzes issue snapshots to determine the correct destination for efficient tracking and resolution.

What is the best way to capture bug context for team triage?

Capturing bug context involves creating structured issue snapshots that preserve environment details and recent activity. This generates human-tractable records in memory to streamline team triage and resolution.

How do I file GitHub issues directly from captured deployment reports?

Filing GitHub issues from deployment reports uses smart routing to evaluate content signals and user input. It determines whether to store the issue in memory or file it directly to GitHub for visibility.

Can I track workflow blockers across multiple services without manual routing?

Tracking workflow blockers across services adapts routing based on content signals to eliminate manual distribution. It captures the report and automatically routes the issue to the correct owner or repository.