gh-issue-report

Automate bug intake, duplicate checks, and issue filing on GitHub via gh CLI.

15|Updated Mar 11, 2026

Search Tags:#automation #templates #github #triage #code investigation #bug #issue filing

Ready to run

npx skills add https://github.com/jackchuka/skills --skill gh-issue-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gh-issue-report
Source: https://github.com/jackchuka/skills/tree/main/gh-issue-report
Command: npx skills add https://github.com/jackchuka/skills --skill gh-issue-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate and file bug reports on GitHub repositories with a structured, repeatable workflow that reduces duplicates and ensures consistency across issues.

Core Features & Use Cases

Intake and target resolution: determine the target repo from user input or current git context, then capture the bug description.
Duplicate detection: search existing issues in parallel to identify potential duplicates before filing.
Conventions verification: fetch contributing guides and issue templates to ensure alignment with repo standards.
Lightweight and optional deep code investigation: perform quick file checks locally or remotely to validate the bug.
Drafting and filing: compose a well-structured issue with title, description, steps to reproduce, environment, and optional root cause or fixes.
Issue creation: file the issue on GitHub via gh CLI and return the resulting URL.
Interaction model: interactive prompts and template-driven drafting adapt to repo conventions and user input.

Quick Start

Run gh-issue-report to begin an interactive bug filing workflow.

Frequently Asked Questions about gh-issue-report

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

FAQPage Schema

How do I automatically file structured GitHub issues from bugs?▼

To automate GitHub issue filing from bugs, you can use a workflow that performs triage, checks for duplicates, and drafts issues according to repo templates. It then uses the gh CLI to create the issue and return the resulting URL.

Can I check for duplicate GitHub issues before filing a new bug report?▼

Yes, duplicate detection searches existing GitHub issues in parallel to identify potential matches before filing. This phased triage process prevents redundant bug reports and ensures consistency across the repository.

Does the automated bug filing process work with local and remote repositories?▼

Yes, the automated bug filing process works with both local and remote repositories. It determines the target repo from user input or current git context and performs quick file checks locally or remotely to validate the bug.

How do I ensure my GitHub bug reports follow repository templates and conventions?▼

To ensure bug reports follow conventions, the workflow fetches contributing guides and issue templates before drafting. It composes a structured issue with title, description, steps to reproduce, and environment that adheres to repo standards.

Do I need the gh CLI installed to file structured issues on GitHub?▼

Yes, the gh CLI is required for repository operations and issue creation. The workflow relies on the gh CLI to file the drafted issue on GitHub and return the resulting URL after the triage and drafting phases are complete.

What is the best way to structure a bug report for GitHub issue tracking?▼

The best way to structure a bug report is using a template-driven drafting approach that includes a title, description, steps to reproduce, environment, and optional root cause or fixes. This ensures alignment with repo conventions during issue filing.