create-gh-issue

Generate structured GitHub issues with root-cause analysis and implementation plans.

8|Updated May 29, 2026
One-click install
npx skills add https://github.com/offlinecv/OfflineCV --skill create-gh-issue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-gh-issue
Source: https://github.com/offlinecv/OfflineCV/tree/main/.claude/skills/create-gh-issue
Command: npx skills add https://github.com/offlinecv/OfflineCV --skill create-gh-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of poorly documented or context-deprived GitHub issues by enforcing a rigorous, self-contained drafting process that ensures every issue includes a root-cause analysis, implementation plan, and clear acceptance criteria.

Core Features & Use Cases

  • Automated Issue Drafting: Generates comprehensive issue bodies with technical design or root-cause analysis sections.
  • Reuse Gate Enforcement: Automatically checks for existing UI components or surfaces to prevent redundant development.
  • Use Case: When a bug is identified in the PDF parser, use this skill to generate a detailed issue that includes the specific file, line numbers, and a step-by-step plan for a contributor to resolve it without needing additional context.

Quick Start

Use the create-gh-issue skill to file a new bug report for the identified PDF parsing failure in the current conversation.

Frequently Asked Questions about create-gh-issue

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

FAQPage Schema
How do I create structured GitHub issues with root-cause analysis automatically?▼

You can create structured GitHub issues by synthesizing conversation context into comprehensive technical plans that include root-cause analysis, implementation steps, and acceptance criteria. This ensures every issue is self-contained with detailed technical design sections.

What's the best way to file a GitHub bug report with implementation steps for contributors?▼

Filing a GitHub bug report with implementation steps requires generating a comprehensive issue body that includes specific file references, line numbers, and a step-by-step resolution plan. This provides contributors the exact context needed without requiring additional information.

Do I need GitHub CLI access to automate issue drafting for feature requests?▼

Yes, you need authenticated GitHub CLI access and local script execution to automate issue drafting for feature requests. This ensures consistent issue formatting and proper metadata application when generating self-contained technical plans.

Can I prevent redundant development when creating GitHub issues for new features?▼

Yes, you can prevent redundant development through reuse gate enforcement, which automatically checks for existing UI components or surfaces before creating a new GitHub issue. This validation step ensures no duplicate work is initiated.

Why do my GitHub issues lack context for contributors to start implementation?▼

GitHub issues lack context when they miss root-cause analysis and implementation plans. By enforcing a rigorous drafting process, every issue synthesizes conversation context into structured technical plans with clear acceptance criteria.

Does the create-gh-issue skill work with local scripts for consistent issue formatting?▼

Yes, the create-gh-issue skill works with local scripts and authenticated GitHub CLI access to ensure consistent issue formatting and metadata application. It generates self-contained issues by synthesizing conversation context into structured technical plans.