github-issues

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

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

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, viewing, labeling, assigning, commenting on, and closing issues directly from the terminal, with both gh CLI and curl REST API variants. ## Core Features & Use Cases - Issue CRUD Operations: List, view, create, comment on, close, and reopen issues using gh commands or authenticated curl calls against the GitHub REST API. - Triage Workflow: A structured 5-step process for listing untriaged issues, categorizing them, applying labels and priorities, and assigning owners. - Bulk Operations: Shell pipelines for batch actions, such as closing all issues carrying a specific label. - Templates: Ready-made bug report and feature request templates in templates/ for consistent issue formatting. - Use Case: When asked to triage a backlog, the agent lists issues labeled needs-triage, reads each one, applies appropriate labels and assignees, and posts triage comments — all without leaving the terminal. ## 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 the gh CLI, send a POST request with curl to /repos/{owner}/{repo}/issues using a GITHUB_TOKEN for authorization.

How to triage GitHub issues with gh CLI?▼

List untriaged issues with `gh issue list --label needs-triage --state open`, read each with `gh issue view`, then apply labels and assignees via `gh issue edit`. Finish by posting triage notes with `gh issue comment`.

gh CLI vs GitHub REST API for issue management?▼

The gh CLI offers shorter, interactive-friendly commands like `gh issue list` and `gh issue close`. The REST API via curl works without installing gh and suits scripted pipelines, but requires manual token handling and JSON parsing.

Can I manage GitHub issues without the gh CLI installed?▼

Yes. Every operation has a curl fallback that calls the GitHub REST API directly. The token is read from GITHUB_TOKEN, the ~/.dag/.env file, or ~/.git-credentials as a fallback.

How do I close multiple GitHub issues at once?▼

Pipe issue numbers from `gh issue list --label wontfix --json number --jq '.[].number'` into `xargs gh issue close`. With curl, loop over numbers from the issues endpoint and send PATCH requests setting state to closed.