github-issues

Create, search, label, assign, comment, and triage GitHub issues via CLI or REST API.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MarbleSodas/Mavis --skill github-issues-marblesodas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/MarbleSodas/Mavis/tree/main/skills/github/github-issues
Command: npx skills add https://github.com/MarbleSodas/Mavis --skill github-issues-marblesodas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines the creation, searching, labeling, assignment, commenting, and triage of GitHub issues so teams spend less time managing backlog and more time fixing software problems.

Core Features & Use Cases

  • Issue viewing and searching: Quickly list, filter, and open specific issues using either the GitHub CLI (gh) or direct GitHub REST API calls.
  • Issue creation with templates: Create well-structured bug reports and feature requests, including labels and assignees, with consistent formatting.
  • Triage and bulk operations: Apply labels and priorities, assign owners, add triage notes, and perform bulk closures for items matching criteria.

Quick Start

Ask the agent to create a new GitHub issue for a bug in your repository, including a title, a formatted body, and the appropriate labels and assignee.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I create and triage GitHub issues in bulk?

GitHub issue triage is supported through bulk operations that apply labels, assign owners, add notes, and close items matching specific criteria using GitHub CLI commands or REST API endpoints.

Can I use the GitHub CLI to search and filter repository issues?

Yes, GitHub CLI commands allow you to quickly list, filter, and view specific issues in a target repository, providing a fast way to manage software project backlogs alongside direct GitHub REST API calls.

How do I create well-structured GitHub bug reports and feature requests?

Creating well-structured GitHub bug reports and feature requests involves generating formatted issue bodies with consistent templates, automatically applying appropriate labels and assignees to streamline backlog management.

Does this approach require authenticated access to perform GitHub issue operations?

Authenticated access to a target repository is required to perform GitHub issue operations, ensuring secure creation, searching, labeling, assignment, commenting, and bulk triage updates across open items.

What is the best way to handle untriaged items in a GitHub backlog?

The best way to handle untriaged GitHub backlog items is applying priority labels, assigning owners, adding triage notes, and performing bulk closures for matching criteria via GitHub CLI or REST API endpoints.