issue

Interview users to create GitHub issues via the gh CLI.

1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/guicaulada/dotfiles --skill issue-guicaulada
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/guicaulada/dotfiles/tree/main/home/dot_claude/exact_skills/issue
Command: npx skills add https://github.com/guicaulada/dotfiles --skill issue-guicaulada

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps users transform vague or incomplete problem reports into clear, actionable GitHub issues by interviewing for missing details, checking for duplicates, and composing a well-structured title and body ready for review.

Core Features & Use Cases

  • Guided Interviewing: Ask targeted follow-up questions based on issue type (bug, feature, docs, chore) to gather essential context.
  • Duplicate Detection & Context Discovery: Search the repository for related or duplicate issues and present options to create, comment, or cancel.
  • Composed Issue Draft & Validation: Generate a concise title and structured body, validate labels against the repository, present an issue preview, and create the issue via the gh CLI.
  • Use Case: When a user reports "login fails on long passwords", the Skill elicits reproduction steps, environment details, checks for existing reports, and opens a ready-to-review issue in the browser.

Quick Start

Create a new GitHub issue by providing a brief description of the problem and answering follow-up questions to produce and open an issue preview.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I create actionable GitHub issues from vague user reports?

To create actionable GitHub issues from vague user reports, a guided interview process asks targeted follow-up questions to gather essential context, checks for duplicates, and composes a structured title and body for review.

What is the best way to check for duplicate GitHub issues before submitting a new bug report?

Checking for duplicate GitHub issues involves searching the repository for related reports during issue creation, presenting options to either create a new issue, comment on an existing one, or cancel the process entirely.

How do I validate repository labels when creating a new feature request via the gh CLI?

Validating repository labels when creating a feature request via the gh CLI involves looking up available repository labels, applying them to the composed issue draft, and presenting a preview confirmation before final issue creation.

Can I use the gh CLI to draft and preview a structured bug report before opening it in the browser?

Yes, you can use the gh CLI to draft and preview a structured bug report by composing a concise title and body, validating labels, and using the preview confirmation step before executing gh issue view --web to open it.

Does issue triage with the gh CLI support classifying different types of GitHub issues?

Issue triage with the gh CLI supports classifying different types of GitHub issues by asking targeted follow-up questions based on the specific issue type, such as bug, feature, docs, or chore, to gather necessary context.