| name | issue-enricher |
| description | Transforms rough requirements into well-structured GitHub issues. Use when the user provides a vague idea, feature request, or problem description and wants to create a GitHub issue. Analyzes codebase, explores solution approaches, researches relevant libraries, and generates actionable issues using `gh` CLI. |
| license | Complete terms in LICENSE.txt |
Process
1. Understand the Requirement
Extract from user input:
- Core problem/goal: What needs to be solved?
- Mentioned constraints: Tech stack, performance, compatibility
- Referenced files/APIs:
@file.yaml, existing code paths
- Related issues: Links to parent or related issues
If the task is enriching an existing GitHub issue rather than creating a new one:
- Treat
docs/issues/ as the local issue knowledge base when it is available
- Search for mirrored GitHub issues and prior local issue reports before proposing a new direction
- Call out duplicate or related issues explicitly in the output
- For related GitHub issues, inspect associated pull requests and summarize the changed files / diff themes when that context is available
2. Codebase Analysis
Search the codebase to understand context:
- Existing patterns for similar features
- Related modules and their architecture
- Relevant configuration files
- Test patterns used in the project
- Existing local issue files under docs/issues/ that provide historical context
- Linked PR file changes for related GitHub issues (fetch via gh when needed)
