github-issues

Create, update, and organize GitHub issues via MCP tools.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/azap026/smetalabv3 --skill github-issues-azap026
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/azap026/smetalabv3/tree/main/.github/skills/github-issues
Command: npx skills add https://github.com/azap026/smetalabv3 --skill github-issues-azap026

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve?

Teams often struggle with inconsistent GitHub issue workflows across repositories, leading to missed bugs, delayed responses, and fragmented collaboration. This Skill automates issue creation, updates, commenting, labeling, and milestone management via MCP tools to unify processes and speed up triage.

Core Features & Use Cases

  • Create and update issues: Generate new issues with structured bodies, add labels, assignees, and milestones.
  • Query and manage issues: List, search, and fetch issue details to support status tracking and reporting.
  • Template-driven bodies: Use standardized templates for bug reports, feature requests, and tasks to ensure consistency across teams.
  • Workflow automation: Integrate with MCP tools or services to automate repetitive triage and updates.

Quick Start

To create a new issue, say: Create an issue in owner/repo with title "Bug: login fails" and body describing steps to reproduce. To add a label or milestone or assignee, include the fields in the request.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I automate GitHub issue creation across multiple repositories?โ–ผ

You can automate GitHub issue creation by using MCP tools to generate new issues with structured bodies, labels, assignees, and milestones. This standardizes workflows across repositories to unify processes and speed up triage.

Can I use standardized templates for bug reports and feature requests in GitHub?โ–ผ

Yes, you can use standardized templates for bug reports, feature requests, and tasks to ensure content consistency. Template-driven bodies structure issue content securely across teams and repositories.

How do I manage GitHub labels, assignees, and milestones automatically?โ–ผ

You can manage GitHub labels, assignees, and milestones automatically by including those fields in your MCP tool request. This allows you to add or update issue metadata seamlessly during creation or modification.

What is the best way to search and list GitHub issues for status tracking?โ–ผ

The best way to search and list GitHub issues for status tracking is using MCP endpoints to query, fetch, and list issue details. This automated retrieval supports reporting and workflow visibility.

Do I need MCP endpoints to automate GitHub issue triage and updates?โ–ผ

Yes, you need MCP endpoints and standardized templates to automate repetitive triage and updates. The automation relies on these MCP tools to securely perform actions like commenting, labeling, and organizing issues.

Why use MCP tooling instead of standard GitHub integrations for issue management?โ–ผ

Using MCP tooling for issue management unifies fragmented processes across repositories, unlike standard integrations. It automates repetitive triage, enforces structured templates, and organizes milestones securely to prevent missed bugs and delayed responses.