skills.rest
gawashi
gawashiCOMMUNITY
Explore all skills by this author →
GitHub

create-github-issue

Capture design problems discovered during implementation into GitHub Issues.

Updated Aug 27, 2026
Search Tags:#automation#workflow#design#planning#github#issues
One-click install
npx skills add https://github.com/gawashi/dotfiles --skill create-github-issue-gawashi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-github-issue
Source: https://github.com/gawashi/dotfiles/tree/main/.claude/skills/create-github-issue
Command: npx skills add https://github.com/gawashi/dotfiles --skill create-github-issue-gawashi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures design deficiencies, contradictions, or oversights discovered during development by turning them into actionable GitHub Issues without interrupting the current task.

Core Features & Use Cases

  • Guided flow to gather context, compose the issue, preview, edit, and create the issue, then resume work.
  • Automatically attaches relevant context and references, and optionally applies labels based on the workflow.
  • Use Case: A developer notices a gap in specs and creates a tracked issue to ensure follow-up and accountability.

Quick Start

Type /create-github-issue and describe the problem to start the flow.

Frequently Asked Questions about create-github-issue

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

FAQPage Schema
How do I create a GitHub issue for a design problem without interrupting my development workflow?▼

A guided flow captures design problems into GitHub issues non-disruptively by gathering context, composing the issue, previewing, editing, and confirming creation before you resume your current development task.

What is the best way to track spec conflicts or edge cases found during implementation?▼

Tracking spec conflicts or edge cases is handled by capturing them as actionable GitHub issues. The workflow automatically attaches relevant context and references, optionally applies labels, and ensures a safe preview and confirm flow before creation.

Do I need GitHub authentication to capture design issues during software development?▼

Yes, GitHub authentication and repository context are required to capture design issues. The workflow uses these prerequisites to apply pre-defined labels and ensure a safe preview, edit, and confirm flow before creating the issue.

How does the preview and confirm flow work when creating GitHub issues from design deficiencies?▼

The preview and confirm flow works by gathering problem context, composing the issue, allowing edits, and requiring confirmation before creation. This ensures a safe, non-disruptive workflow for capturing design deficiencies during implementation.

Can I automatically apply labels to GitHub issues created for missing specifications?▼

Yes, labels can be automatically applied to GitHub issues created for missing specifications. The guided workflow optionally applies labels based on pre-defined workflows while attaching relevant context and references to the issue.

Related Skills

Explore More Software Engineering Skills→
tomzxtomzx
5

label-issue

Read a GitHub issue and apply relevant existing labels.

Community
Intermediate
Eigo-Mt-FujiEigo-Mt-Fuji

bug-hunter

Guide structured bug investigation and root cause analysis with verification steps.

Community
Advanced
prof-danielcprof-danielc

speckit.quizme

Analyze feature specifications with Socratic questioning to detect logical gaps and edge cases.

Community
Advanced
apacheapache
79

magpie-issue-deduplicate

Identify and merge duplicate issues in issue trackers with maintainer confirmation.

Official
Intermediate