issue

Create GitHub issues from user input with duplicate checks and milestone assignment.

3|1|Updated Feb 18, 2026

Search Tags:#github #milestones #issue #triage #capture #dedup #stabilization

Ready to run

npx skills add https://github.com/corrigantj/buehler --skill issue-corrigantj

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Fast capture: convert user input into a structured GitHub issue with a lightweight initial body.
Dedup and milestone context: checks for duplicates and assigns the appropriate milestone or marks as standalone when needed.
Stabilization-aware: detects stabilization context and links to the relevant stabilization ticket when present.
Gate-driven workflow: presents next-step options (add description, run investigation, or both) before deeper analysis.
Backlog support: handles backlog ideas as separate issues with proper labeling and tracking.

Quick Start

Describe an issue and the skill will create a fast-capture GitHub issue with an investigation gate.

Frequently Asked Questions about issue

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

FAQPage Schema

How do I quickly capture and triage GitHub issues from user input?▼

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.

What is issue triage and how does deduplication work with GitHub milestones?▼

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.

How do I link a GitHub issue to a stabilization ticket?▼

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.

Does this issue triage workflow require reading local files or repositories?▼

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.

What is the best way to manage backlog ideas as separate GitHub issues?▼

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.

What steps follow after creating a fast-capture GitHub issue?▼

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.