github-issue-creator

Create structured GitHub issues with problem, impact, and acceptance criteria.

15|1|Updated Sep 13, 2025
One-click install
npx skills add https://github.com/EdanStarfire/claudecode_webui --skill github-issue-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-creator
Source: https://github.com/EdanStarfire/claudecode_webui/tree/main/.claude/skills/github-issue-creator
Command: npx skills add https://github.com/EdanStarfire/claudecode_webui --skill github-issue-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This Skill ensures GitHub issues are well-structured, problem-focused, and outcome-oriented, preventing vague requirements and premature implementation details. It helps you define clear, testable tasks that lead to successful development.

Core Features & Use Cases

  • Problem Definition: Clearly articulate the user's problem, current behavior, and desired outcome from a user perspective.
  • Impact Analysis: Detail user and business impact to justify the issue's importance and prioritize work effectively.
  • Testable Acceptance Criteria: Define objective, verifiable criteria for when the issue is considered "done," ensuring clarity for testing and sign-off.
  • Use Case: When a user reports "the login page is broken," use this Skill to ask clarifying questions and then create an issue that describes the problem (e.g., "users cannot log in with valid credentials"), its impact, and testable acceptance criteria, rather than immediately suggesting a technical solution.

Quick Start

Create a GitHub issue for a bug where "WebSocket connection fails to reconnect after network interruption," ensuring it includes current/expected behavior, user impact, and clear acceptance criteria.

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 well-structured GitHub issues from bug reports?

Create GitHub issues by defining the problem, current behavior, expected behavior, impact, and testable acceptance criteria rather than jumping to implementation. This Skill automates converting user reports into structured issues that separate concerns between problem definition, implementation planning, and PR descriptions, ensuring clarity for development and testing.

What should GitHub issues include to make them actionable?

Actionable GitHub issues must include the user's problem statement, current behavior, expected behavior, user impact, business impact, and objective acceptance criteria. This Skill enforces the WHAT and WHY principle, preventing vague requirements and premature technical solutions while supporting testable sign-off conditions.

How do I prevent vague requirements when documenting feature requests in GitHub?

Use a template-driven structure that separates problem definition from implementation details. This Skill asks clarifying questions about user needs, impact, and acceptance criteria before creating the issue, ensuring feature requests are outcome-oriented and testable rather than solution-focused.

Can I use this with the GitHub CLI to automate issue creation?

Yes, this Skill integrates with the gh CLI dependency to automate structured GitHub issue creation. It applies the problem-focused template and acceptance criteria framework through gh commands, streamlining the workflow from user report to formatted issue.

What's the difference between defining requirements and writing implementation plans?

Requirements define WHAT the user needs and WHY it matters; implementation plans define HOW to build it. This Skill enforces this separation by creating issues that focus on problem, impact, and testable acceptance criteria—leaving technical approach decisions for the implementation phase.