create-issue

Creates a GitHub issue via the gh CLI without implementing the described work.

51|19|Updated Jan 4, 2025
One-click install
npx skills add https://github.com/HeliosSoftware/hfs --skill create-issue-heliossoftware
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-issue
Source: https://github.com/HeliosSoftware/hfs/tree/main/.claude/skills/create-issue
Command: npx skills add https://github.com/HeliosSoftware/hfs --skill create-issue-heliossoftware

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you spot a bug or want to capture work for later, context-switching to fix it immediately derails your current task. This Skill files a well-structured GitHub issue grounded in real code references, then stops — so the work is captured without being started. ## Core Features & Use Cases - Grounded issue writing: Performs read-only investigation (grep, git log, gh) to cite exact files and line numbers in the issue body. - Duplicate and label checks: Searches existing issues before creating one and only applies labels that already exist in the repository. - Structured issue templates: Produces Summary, Current/Expected behavior, Evidence, and Suggested approach sections, or Motivation and Acceptance criteria for feature requests. - Use Case: While reviewing code you notice a slug validation bug. Ask the Skill to file an issue; it locates the offending line, checks for duplicates, creates the issue with the bug label, and returns the URL without touching any source file. ## Quick Start Ask the assistant to open a GitHub issue describing the bug you found, including what file it occurs in and what behavior you expected.

Frequently Asked Questions about create-issue

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

FAQPage Schema
How do I create a GitHub issue from the command line?▼

Use gh issue create with a title and a body file, for example gh issue create --title "..." --body-file issue-body.md --label bug. Writing the body to a file first avoids shell-quoting problems with backticks and newlines.

How do I check for duplicate GitHub issues before filing?▼

Run gh issue list --search "<keywords>" --state all --limit 20 to find existing open and closed issues. If a close match appears, comment on it instead of opening a new one.

Why does gh issue create fail when I add labels?▼

The gh CLI rejects labels that do not already exist in the repository. Run gh label list --limit 100 first and only apply labels from that list, or apply none when nothing fits.

Can this Skill fix the bug after creating the issue?▼

No. The Skill explicitly stops after printing the issue URL and never edits source files, runs builds, or opens branches. Any fix must be requested in a separate turn.

What should a good GitHub issue body include?▼

Include a Summary, Current behavior with the exact trigger, Expected behavior, and Evidence citing file paths with line numbers. An optional Suggested approach section captures fix ideas for whoever picks up the issue.