github-issue-create

Verify claims in draft material and create a labeled GitHub Issue from templates.

1|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/mjun0812/skills --skill github-issue-create-mjun0812
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-create
Source: https://github.com/mjun0812/skills/tree/main/skills/github/github-issue-create
Command: npx skills add https://github.com/mjun0812/skills --skill github-issue-create-mjun0812

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning loose todos, memos, and bug reports into well-structured GitHub Issues requires manual fact-checking, template selection, and label assignment, which often results in vague or inaccurate issues. ## Core Features & Use Cases - Claim Verification: Extracts verifiable claims from your draft and checks them against the repository (Glob/Grep/Read, git log/blame) and official external docs before writing anything. - Automatic Classification: Selects the right issue type (bug report, feature request, task, test, research) and matching labels from the repository's existing label set. - Duplicate Detection: Searches open and closed issues for related work and links them with Related to #N instead of creating duplicates. - Use Case: After a debugging session, ask to file a bug report; the Skill verifies the error path in code, picks the bug template, attaches verified references, and creates the issue after your approval. ## Quick Start Ask the assistant to turn the current conversation's findings into a GitHub issue, for example by saying "verify this bug report and create an issue for it".

Frequently Asked Questions about github-issue-create

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

FAQPage Schema
How do I create a GitHub issue from a draft or memo?

Provide the draft text in your request and the Skill verifies its claims against the repository, selects a template, and drafts the issue. It asks for your approval before running gh issue create.

How does the Skill verify claims before filing an issue?

It extracts verifiable statements about files, functions, commands, and errors, then checks them with Glob, Grep, Read, git log, and git blame. External tool or library claims are checked against official docs via web search, and each claim is classified as verified, inferred, or unconfirmed.

Does it support repositories with their own issue templates?

Yes. If .github/ISSUE_TEMPLATE/ exists in the repository, those templates take priority. Otherwise it falls back to bundled English or Japanese templates for bug reports, feature requests, tasks, tests, and research.

Can it create issues in Japanese?

Yes. Pass the language argument as "ja" to generate the title and body in Japanese using the bundled Japanese templates. The default language is English.

What happens if a similar issue already exists?

It searches open and closed issues with keywords from your draft. If a matching open issue exists, it asks whether to proceed or cancel; closed matches are linked as Related to #N with a note that the problem may already be resolved.

Why does it refuse to create the issue immediately?

The Skill always presents the generated title, body, type, and labels for approval before creation. This prevents publishing unverified claims, private repository references, or misclassified issues to a public tracker.