github-issues

Creates, lists, labels, assigns, comments on, and closes GitHub issues via gh or REST API.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/devMoez/titan --skill github-issues-devmoez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/devMoez/titan/tree/main/skills/github/github-issues
Command: npx skills add https://github.com/devMoez/titan --skill github-issues-devmoez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issue management can become slow and inconsistent when creating, labeling, assigning, commenting, and closing issues across teams.

Core Features & Use Cases

  • Issue discovery: List, filter by labels/state/assignee, and search issues to quickly find relevant work.
  • Issue creation: Create well-structured bug reports and feature requests with labels and assignees.
  • Triage workflow: Apply priority/triage labels, assign ownership, and add commentary to keep backlog hygiene.
  • Lifecycle actions: Comment, close/reopen, and support issue-to-PR linking patterns like “Closes #N”.

Quick Start

Ask the agent to create a GitHub issue for a bug in the current repository using the provided title, steps to reproduce, and labels (it will use GitHub CLI if available, otherwise it will fall back to the GitHub REST API).

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I automate creating and triaging GitHub issues?

You can automate creating and triaging GitHub issues by using an agent to generate well-structured bug reports, apply priority labels, assign ownership, and add commentary using GitHub CLI or REST API calls.

What is the best way to manage GitHub issue backlogs in bulk?

Managing GitHub issue backlogs in bulk is handled through listing, filtering by labels or assignee, searching issues, and performing bulk lifecycle actions like closing or reopening tickets via GitHub REST API endpoints.

Does this issue triage workflow require GitHub CLI?

GitHub issue triage does not strictly require GitHub CLI; the workflow uses GitHub CLI if available, but automatically falls back to GitHub REST API calls for issue management and labeling tasks.

Can I link GitHub issues to pull requests during issue lifecycle management?

Linking GitHub issues to pull requests during issue lifecycle management is supported using issue-to-PR linking patterns like “Closes #N” when commenting, closing, or updating tickets in your repository.

What do I need for GitHub repository authentication to manage issues?

GitHub authentication and repository owner/name resolution are required before managing issues, ensuring safe API usage with correctly constructed endpoints for issues and labels in your target repository.