github-issues

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

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/Chensihakniroth/ANAKOT-AGENT --skill github-issues-chensihakniroth
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/Chensihakniroth/ANAKOT-AGENT/tree/main/skills/github/github-issues
Command: npx skills add https://github.com/Chensihakniroth/ANAKOT-AGENT --skill github-issues-chensihakniroth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing GitHub issues manually through the web UI is slow and hard to automate. This Skill lets you create, search, label, assign, comment on, and close issues directly from the command line using either the gh CLI or the GitHub REST API. ## Core Features & Use Cases - Full Issue Lifecycle: Create issues with structured bug report and feature request templates, then label, assign, comment, close, or reopen them. - Dual Execution Paths: Every operation shows the gh CLI command first with a curl/REST API fallback, so it works whether or not gh is installed. - Triage & Bulk Operations: List untriaged issues, categorize them, apply labels and priorities, and run batch operations like closing all issues with a given label. - Use Case: Ask the agent to triage all open issues labeled "needs-triage" in your repository, and it will read each one, apply appropriate labels and assignees, and post triage notes automatically. ## Quick Start List all open issues labeled bug in this repository and create a new issue for the login redirect problem 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. Without gh, send a POST request with curl to /repos/{owner}/{repo}/issues using your GITHUB_TOKEN for authorization.

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, and comment with triage notes. Bulk operations combine gh issue list --json with xargs.

gh CLI vs GitHub REST API for issue management?▼

The gh CLI offers shorter commands and built-in authentication, while the REST API with curl works in environments where gh is not installed. This Skill documents both paths for every operation, including a quick reference table mapping each action.

Does this work without the gh CLI installed?▼

Yes, every operation includes a curl fallback using the GitHub REST API. You need a GITHUB_TOKEN, which the setup script reads from the environment, ~/.anakot/.env, or ~/.git-credentials.

Why does the GitHub issues API return pull requests?▼

The GitHub REST API /issues endpoint includes pull requests because PRs are internally issues. The provided curl examples filter them out by checking for the pull_request key in each returned item before printing results.

How do I close GitHub issues automatically when merging a PR?▼

Include keywords like Closes #42, Fixes #42, or Resolves #42 in the pull request body, and GitHub closes the linked issue on merge. You can also create a branch from an issue with gh issue develop 42 --checkout.