github-issues

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

115|9|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/AtlasOmnia/donna-starter --skill github-issues-atlasomnia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/AtlasOmnia/donna-starter/tree/main/skills/github/github-issues
Command: npx skills add https://github.com/AtlasOmnia/donna-starter --skill github-issues-atlasomnia

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 using either the gh CLI or the GitHub REST API. ## Core Features & Use Cases - Issue CRUD Operations: Create, view, comment on, close, and reopen issues with gh commands or curl fallbacks. - Triage Workflow: List untriaged issues, categorize them, apply labels and priorities, and assign owners in a structured process. - Bulk Operations: Batch-close or batch-update issues by combining API calls with shell scripting. - Templates Included: Ready-made bug report and feature request templates for consistent issue quality. - Use Case: You need to triage 30 open issues in a repository. Use the triage workflow to list issues labeled needs-triage, categorize each one, apply priority labels, and assign owners without leaving the terminal. ## Quick Start Ask the assistant 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 to file an issue from the terminal. Alternatively, send a POST request with curl to /repos/{owner}/{repo}/issues using a GITHUB_TOKEN for authentication.

How to triage GitHub issues with gh CLI?

List untriaged issues with gh issue list --label needs-triage --state open, then read each issue, apply labels with gh issue edit --add-label, assign owners with --add-assignee, and add triage notes via gh issue comment.

gh CLI vs GitHub REST API for issue management?

The gh CLI offers shorter, authenticated commands ideal for interactive use, while the REST API with curl works in environments without gh installed. This Skill provides both variants for every operation, so either approach covers the same functionality.

Can I close multiple GitHub issues at once?

Yes, bulk operations combine issue listing with shell loops. Pipe gh issue list --json number output to xargs with gh issue close, or iterate over curl-fetched issue numbers and PATCH each issue's state to closed.

Why does the GitHub issues API return pull requests?

The GitHub REST API treats pull requests as issues, so GET /repos/{owner}/{repo}/issues includes PRs in results. Filter them out by checking for the pull_request key in each returned item, as shown in the Skill's Python parsing snippets.

What authentication is required for GitHub issue commands?

Either an authenticated gh CLI session (verified with gh auth status) or a GITHUB_TOKEN environment variable is required. The token can be stored in the Hermes .env file; plaintext git-credentials files are intentionally not used.