issue-create

Create GitHub Issues with duplicate checks and template alignment.

Updated May 31, 2026
One-click install
npx skills add https://github.com/shoji9x9/skills --skill issue-create-shoji9x9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-create
Source: https://github.com/shoji9x9/skills/tree/main/.agents/skills/issue-create
Command: npx skills add https://github.com/shoji9x9/skills --skill issue-create-shoji9x9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Manually creating GitHub Issues often leads to inconsistent formatting, duplicate tickets, missing context, and accidental misposts that waste development team time and create tracking overhead.

Core Features & Use Cases

  • Duplicate Check: Scans open issues before creation to avoid redundant tickets.
  • Template Alignment: Auto-detects and uses repository-specific issue templates, or falls back to built-in templates for consistent structure.
  • Approval Gate: Requires user confirmation of draft content before posting to prevent errors.
  • Use Case: For development teams that need to quickly log bugs, feature requests, and tasks as well-structured GitHub Issues without manual formatting or duplicate tracking.

Quick Start

Use the issue-create skill to create a GitHub Issue for the login screen crashing during SSO, and get my approval before posting it.

Frequently Asked Questions about issue-create

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

FAQPage Schema
How do I standardize GitHub Issues and avoid duplicate tickets in my development workflow?

To standardize GitHub Issues, you can apply repository-specific .github/ISSUE_TEMPLATE/ directories or built-in fallback templates. This enforces consistent structure for bugs and feature requests, while scanning open issues beforehand prevents redundant tickets.

How does duplicate checking work before creating a GitHub Issue?

Duplicate checking scans open GitHub Issues before creating a new ticket to identify redundant entries. This prevents logging identical bugs or feature requests, reducing tracking overhead and saving development team time.

Do I need GitHub CLI installed to automate issue creation with templates?

Yes, you need GitHub CLI (gh) v2.90.0 or later installed to automate issue creation. This ensures the system can interact with your repository to scan existing issues, apply templates, and submit the final approved draft.

Can I use repository-specific issue templates for logging bugs and feature requests?

Yes, the system auto-detects and uses repository-specific .github/ISSUE_TEMPLATE/ directories for logging bugs and feature requests. If no repository templates exist, it falls back to built-in templates to ensure structured issue content.

What is the best way to prevent accidental misposts when logging GitHub Issues?

The best way to prevent misposts is using an approval gate that requires user confirmation of draft content before posting. This allows you to review the standardized issue, verify duplicate checks, and approve before submission.

What happens if my repository does not have an .github/ISSUE_TEMPLATE/ directory configured?

If your repository lacks an .github/ISSUE_TEMPLATE/ directory, the system falls back to built-in templates. This ensures your GitHub Issues still maintain a consistent structure for tasks, bugs, and feature requests without manual formatting.