github-create-issue

Create GitHub issues with template matching and automatic tool selection.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, yaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill automates the creation of GitHub issues by selecting the best available creation tool (MCP Server, GitHub CLI, or REST API) and by applying templates from the repository's .github/ISSUE_TEMPLATE directory when available. It reduces manual overhead, ensures consistency across projects, and streamlines issue intake for teams.

Core Features & Use Cases

  • Intelligent template matching that selects the most relevant template based on the user's description.
  • Deterministic tool selection with sensible fallbacks: MCP Server when available, then gh CLI, then REST API.
  • Template loading support and metadata handling (labels, assignees, milestones) to auto-populate issue fields.

Quick Start

Create a GitHub issue titled "Sample issue" with a descriptive body to demonstrate automatic template matching and tool selection.

Frequently Asked Questions about github-create-issue

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

FAQPage Schema
How do I automate GitHub issue creation using repository templates?

Automating GitHub issue creation uses a keyword-based scoring system to match user descriptions against .github/ISSUE_TEMPLATE files, auto-populating labels, assignees, and milestones while selecting the best available tool like MCP Server, gh CLI, or REST API.

What's the best way to match an issue description to a GitHub template automatically?

Matching an issue description to a GitHub template uses keyword-based scoring to evaluate .github/ISSUE_TEMPLATE files, picking the best-fitting template automatically or proposing options when the description is ambiguous.

Do I need a GITHUB_TOKEN to create issues via the REST API?

Creating issues via the REST API requires authentication using GITHUB_TOKEN or GH_TOKEN environment variables, though the workflow can also use gh CLI authentication or an MCP Server if available before falling back to the REST API.

How does the tool selection fallback work between MCP Server, gh CLI, and REST API?

Tool selection for GitHub issue creation follows a deterministic fallback order: it uses the MCP Server when available, then falls back to the gh CLI, and finally uses the REST API to ensure reliable automation.

Can I auto-populate issue labels and assignees from template metadata?

Auto-populating issue labels, assignees, and milestones is supported by loading and parsing metadata from .github/ISSUE_TEMPLATE files during the automated GitHub issue creation process.

What happens when multiple GitHub issue templates match my description?

When multiple GitHub issue templates match a description ambiguously, the keyword-based scoring system proposes template options for the user to choose from rather than forcing a single selection.