github-issue-creator

Create structured GitHub issues with Summary, Context, and Acceptance Criteria.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/lutzcc1/claude-skills --skill github-issue-creator-lutzcc1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-creator
Source: https://github.com/lutzcc1/claude-skills/tree/main/user/github-issue-creator
Command: npx skills add https://github.com/lutzcc1/claude-skills --skill github-issue-creator-lutzcc1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users convert user requests into fully-formed GitHub issues, ensuring consistent structure and context for future Claude work.

Core Features & Use Cases

  • Structured Issue Templates: Generate well-organized issues that include Summary, Context, Current State, Desired State, Acceptance Criteria, Technical Notes, and Related Files.
  • Contextual Documentation: Capture task details, files, and constraints so another Claude instance can pick up and implement.
  • Use Case: When a user asks to document a bug or feature, this skill produces a ready-to-create GitHub issue you can paste or push with the provided template.

Quick Start

Use the github-issue-creator skill to document a bug in the repository and generate a GitHub issue template with all required sections.

Frequently Asked Questions about github-issue-creator

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

FAQPage Schema
How do I create structured GitHub issues for bugs and feature requests?

To create structured GitHub issues, you can use this skill to automate generating templates from user requests. It captures context, file references, and constraints, producing sections like Summary, Desired State, and Acceptance Criteria ready for execution.

What is the best way to document a bug for future Claude work on GitHub?

Documenting a bug for future Claude work requires capturing precise context and constraints. This skill generates a consistent template with Current State, Desired State, and Technical Notes, enabling another Claude instance to pick up and implement the task.

How do I ensure my feature request includes all necessary context for developers?

Ensuring a feature request includes necessary context involves documenting task details and related files. This skill applies a structured template with Summary, Context, Acceptance Criteria, and Technical Notes to capture all required constraints for future implementation.

Can I use this skill to automate issue creation for any GitHub repository task?

Yes, you can use this skill to automate issue creation for any repository task. It applies to bugs, features, and general tasks needing future execution, converting user requests into ready-to-create GitHub issues with a consistent template.

What sections are included in a structured GitHub issue template?

A structured GitHub issue template includes Summary, Context, Current State, Desired State, Acceptance Criteria, Technical Notes, and Related Files. These sections ensure consistent structure and comprehensive context for future development work.

Why do I need a structured format for reporting bugs on GitHub?

A structured format for reporting bugs is needed to ensure consistent context capture. This skill generates templates with defined sections like Current State and Acceptance Criteria, preventing missing information and allowing another developer or Claude instance to implement the fix.