Create GitHub issues from user input with duplicate checks and milestone assignment.
npx skills add https://github.com/corrigantj/buehler --skill issue-corrigantj
Please help me install this Agent Skill. Skill: issue Source: https://github.com/corrigantj/buehler/tree/main/skills/issue Command: npx skills add https://github.com/corrigantj/buehler --skill issue-corrigantj
Capturing and triaging issues manually is error-prone and slow; this skill provides a fast, gate-guarded way to create GitHub issues from user input and prepare them for further investigation.
Describe an issue and the skill will create a fast-capture GitHub issue with an investigation gate.
High-intent search queries and answers about installing and using this skill.
You can capture and triage GitHub issues by converting user input into a structured issue with a lightweight body. This process includes de-duplication checks, milestone assignment, and an explicit investigation gate before deeper analysis begins.
Issue triage involves reviewing and categorizing incoming reports, while deduplication searches existing GitHub issues to prevent duplicates. The system then assigns the appropriate milestone or marks the issue as standalone to maintain backlog organization.
To link a GitHub issue to a stabilization ticket, the system detects stabilization context during capture and automatically links the newly created issue to the relevant stabilization reference using GitHub API calls.
No, this issue triage workflow does not require reading local files. It exclusively uses GitHub API calls to read milestones, search for duplicates, create issues, and link stabilization references directly from user input.
The best way to manage backlog ideas is to capture them as separate GitHub issues with proper labeling and tracking. This approach supports distinct capture, fix, and backlog workflows without mixing active investigations.
After creating a fast-capture GitHub issue, a gate-driven workflow presents next-step options. You can choose to add a description, run an investigation, or both before proceeding to deeper analysis and stabilization.
voidrotManage GitHub issues via API and MCP tools.
allaydesaiCoordinate sprint planning, story development, and retrospectives for Agile workflows.
dejavoo21Coordinate GitHub issues, boards, and milestones across teams with swarm-based task orchestration.
Terry-MaoAnalyze GitHub issue closure patterns to propose deduplication guidance updates.
