github-issues

Manage GitHub issues and automate creation, updates, comments, and searches.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/webmaxru/octocat_supply --skill github-issues-webmaxru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/webmaxru/octocat_supply/tree/main/.github/skills/github-issues
Command: npx skills add https://github.com/webmaxru/octocat_supply --skill github-issues-webmaxru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates and structures GitHub issue workflows to eliminate manual, error-prone issue creation, updates, and triage so teams can track bugs and feature requests consistently.

Core Features & Use Cases

  • Issue Creation: Build clear, template-driven bug reports, feature requests, or tasks with titles, bodies, labels, assignees, and milestones.
  • Issue Management: Update existing issues, change state, add comments, and preserve unchanged fields by fetching current issue data first.
  • Search & Triage: Search and list repository issues to identify duplicates, link related work, and support prioritization during triage.
  • Use Case: A developer or product manager files a high-priority bug with a structured reproduction template, assigns maintainers, and links related issues for faster resolution.

Quick Start

Create a bug issue in owner/repo titled [Bug] Login page crashes when using SSO with labels bug and assignee alice.

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 for bug reports and feature requests?

Automate GitHub issue creation by using template-driven workflows to build structured bug reports and feature requests with titles, bodies, labels, assignees, and milestones. This eliminates manual entry errors and ensures consistent issue tracking across your repositories.

Can I update existing GitHub issues and add comments without overwriting current data?

Update existing GitHub issues by fetching current issue data first to preserve unchanged fields. You can change issue state, add comments, modify labels, and update assignees while maintaining the original issue context and avoiding data loss during triage.

Do I need an MCP GitHub server to manage repository issues and perform triage?

Yes, managing repository issues requires access to an MCP GitHub server to perform API operations. You also need repository context including the owner and repo name, plus issue parameters like title, body, labels, assignees, and milestone for successful issue management.

What's the best way to search and list GitHub issues to identify duplicates during triage?

Search and list GitHub repository issues to identify duplicates, link related work, and support prioritization during triage. This structured search approach helps developers and product managers filter issues by labels, assignees, and milestones for faster resolution.

How does issue management handle assigning labels and milestones to new bug reports?

Issue management handles assigning labels and milestones by applying specified parameters like bug, high-priority, or milestone names directly during issue creation. This structured assignment supports immediate triage categorization and maintainers receive instant notifications for faster resolution.

Can I link related GitHub issues when filing a high-priority bug report?

Link related GitHub issues during bug report filing by searching existing repository issues to identify duplicates and connections. This search capability supports triage activities by connecting related work, providing context for maintainers, and prioritizing development tasks effectively.