issue

Generates GitHub-issue Markdown with template-aware title and body from provided requirements.

8|2|Updated May 3, 2026
One-click install
npx skills add https://github.com/ejoongseok/claude-settings --skill issue-ejoongseok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/ejoongseok/claude-settings/tree/main/claude-code/skills/issue
Command: npx skills add https://github.com/ejoongseok/claude-settings --skill issue-ejoongseok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns scattered conversation context and requirements into a ready-to-paste GitHub issue in the correct template style, without creating the issue automatically.

Core Features & Use Cases

  • Issue markdown generation: Produces a complete GitHub issue title and body in Markdown based on the provided or inferred project details.
  • Template-aware formatting: Detects and follows existing templates from .github/ISSUE_TEMPLATE/* (or falls back to a default structure when missing).
  • Issue type classification: Chooses the appropriate issue type (new feature, feature change, bug, publishing, or other) using input signals and adds the right title prefix and structure.
  • External-public documentation rules: Applies the repository’s external-facing writing constraints (e.g., no internal paths/constants, evidence guidance, and checklist-first approach).

Quick Start

Use the issue skill by providing your desired change or bug report details in $ARGUMENTS, and it will output a GitHub-ready issue title and body in Markdown while also saving it to the configured local issues directory.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I generate a GitHub issue from a conversation context or feature request?

To generate a GitHub issue from conversation context, provide your requirements and the tool outputs a ready-to-paste Markdown title and body using a default structure or detected templates.

How do I make my bug report match existing GitHub issue templates automatically?

Your bug report matches existing GitHub issue templates automatically by detecting configurations in `.github/ISSUE_TEMPLATE/*` and applying the corresponding structure, title prefix, and checklist format.

Does this issue generator write directly to GitHub or just output Markdown text?

This issue generator only outputs the Markdown text without writing directly to GitHub, ensuring you review the structured checklist and title prefix before pasting it into your repository.

What is the best way to structure a feature development checklist for a GitHub issue?

The best way to structure a feature development checklist is to classify the issue type, apply the correct title prefix, and generate a Markdown checklist using your project's external-facing documentation rules.

Can I use local project documentation like CLAUDE.md to provide context for issue generation?

Yes, you can use local project documentation because the generator performs optional context reads from CLAUDE.md and other local docs to inform the Markdown issue structure and requirements.

What happens if my repository does not have any issue templates configured?

If your repository has no issue templates configured, the generator falls back to a default Markdown structure that includes a title prefix and a structured checklist for your bug report or feature request.