github-issues

Create, triage, label, and manage GitHub issues via gh CLI or REST API.

1|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/Lento47/arcana-community --skill github-issues-lento47
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/Lento47/arcana-community/tree/main/skills/github/github-issues
Command: npx skills add https://github.com/Lento47/arcana-community --skill github-issues-lento47

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing GitHub issues manually through the web UI is slow and hard to automate. This Skill provides ready-to-use commands for creating, searching, labeling, assigning, and closing issues directly from the terminal, with both gh CLI and curl REST API fallbacks. ## Core Features & Use Cases - Issue CRUD Operations: List, view, create, comment on, close, and reopen issues using gh commands or authenticated GitHub REST API calls. - Triage Workflow: Follow a structured process to list untriaged issues, categorize them, apply labels and priorities, and assign owners. - Bulk Operations & Templates: Batch-close issues by label with shell scripting, and use included bug report and feature request templates for consistent issue quality. - Use Case: When asked to triage a backlog, the agent lists all needs-triage issues, reads each one, applies appropriate labels like bug or priority:high, assigns owners, and posts triage comments automatically. ## Quick Start Ask the agent to list all open issues labeled bug in the current repository and create a new issue using the bug report template.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I create a GitHub issue from the command line?▼

Use `gh issue create` with --title, --body, --label, and --assignee flags. Without gh, send a POST request with curl to /repos/{owner}/{repo}/issues using your GITHUB_TOKEN for authentication.

How to triage GitHub issues automatically?▼

List open issues with the needs-triage label using `gh issue list --label needs-triage`, read each issue to categorize it, then apply labels, set priority, assign owners, and add triage comments with `gh issue edit` and `gh issue comment`.

gh CLI vs GitHub REST API for issue management?▼

The gh CLI offers simpler syntax and handles authentication automatically. The REST API with curl works as a fallback when gh is unavailable, requiring a GITHUB_TOKEN and manual JSON parsing with python3.

Can I close multiple GitHub issues at once?▼

Yes, combine issue listing with shell scripting. Pipe issue numbers from `gh issue list --label wontfix --json number` into `gh issue close`, or loop over curl PATCH requests setting state to closed for each issue number.

Why does the GitHub issues API return pull requests?▼

The GitHub REST API /issues endpoint includes pull requests because PRs are internally issues. Filter them out by checking for the pull_request key in each returned item, as shown in the python3 parsing snippets.