github-issue

Create, list, and close GitHub issues via gh CLI scripts.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/mkrlabs/specflow --skill github-issue-mkrlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue
Source: https://github.com/mkrlabs/specflow/tree/main/examples/.claude/skills/github-issue
Command: npx skills add https://github.com/mkrlabs/specflow --skill github-issue-mkrlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

GitHub issues are the canonical way to track work; this skill lets you generate, organize, and close issues directly from task descriptions or AI conversations.

Core Features & Use Cases

  • Create issues from user tasks described in natural language.
  • List open or closed issues and filter by label or assignee.
  • Close issues with context-aware reasons and optional deletion, facilitating progress tracking and triage.

Quick Start

Describe the task to create an issue and run the create-issue script to publish it.

Frequently Asked Questions about github-issue

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

FAQPage Schema
How do I create GitHub issues from natural language task descriptions?

To create GitHub issues from natural language, you can use an AI task planning workflow that parses conversation context and executes a script to publish the issue directly to your repository.

Do I need the gh CLI installed and authenticated to manage GitHub issues via AI workflows?

Yes, you need the gh CLI installed and authenticated to manage GitHub issues via AI workflows. The automation relies on gh CLI fallbacks to execute operations like creating, listing, and closing issues.

Can I list and filter open GitHub issues by label or assignee from an AI conversation?

You can list and filter open or closed GitHub issues by label or assignee from an AI conversation by running a dedicated script that queries your repository and returns the filtered tracking items.

What is the best way to close resolved GitHub issues with context-aware reasons?

The best way to close resolved GitHub issues with context-aware reasons is using an automated script that closes items based on AI conversation context, optionally deleting the issue to facilitate progress tracking and triage.

Does managing GitHub issues through MCP integration require jq alongside gh?

Managing GitHub issues through MCP integration requires both jq and gh. The MCP-first flows utilize jq to parse JSON outputs and gh to execute the CLI commands for tracking work.

Why use MCP-first flows for GitHub issue tracking instead of manual CLI commands?

Using MCP-first flows for GitHub issue tracking instead of manual CLI commands allows you to automate task planning workflows directly from AI context, generating, organizing, and closing issues without leaving your conversation.