github-issues

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

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/jamsdoescode/Erik-s-Portfolio --skill github-issues-jamsdoescode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/jamsdoescode/Erik-s-Portfolio/tree/main/openclicky/AppResources/OpenClicky/OpenClickyBundledSkills/github-issues
Command: npx skills add https://github.com/jamsdoescode/Erik-s-Portfolio --skill github-issues-jamsdoescode

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 - Issue CRUD Operations: Create, view, search, comment on, close, and reopen issues with gh commands or curl fallbacks. - Triage Workflow: List untriaged issues, apply labels and priorities, assign owners, and post triage notes. - Bulk Operations: Batch-close or batch-update issues by combining API calls with shell scripting. - Use Case: After a bug report comes in, ask the assistant to create a labeled issue with a structured bug report template, assign it to the backend owner, and link it to the fixing pull request. ## Quick Start Create a GitHub issue titled "Login redirect ignores next parameter" labeled as a bug in the current repository.

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, or send a POST request to /repos/{owner}/{repo}/issues with a JSON body containing title, body, labels, and assignees.

How do I triage GitHub issues with labels and assignees?

List open issues with the needs-triage label, read each issue, then apply labels with gh issue edit --add-label, assign owners with --add-assignee, and comment with triage notes before closing or escalating.

gh CLI vs GitHub REST API for issue management?

The gh CLI is simpler when installed and authenticated, handling auth and repo detection automatically. The curl REST API approach works as a fallback when gh is unavailable, using a GITHUB_TOKEN for authorization.

Does this work without the gh CLI installed?

Yes. Every operation has a curl fallback that calls the GitHub REST API directly. You need a GITHUB_TOKEN, which can be read from an environment variable, a .env file, or ~/.git-credentials.

Why does the issues API also return pull requests?

The GitHub /issues endpoint includes pull requests because PRs are internally issues. Filter them out by checking for the pull_request key in each returned item before processing results.

How do I close multiple GitHub issues at once?

List issue numbers matching a label with gh issue list --json number --jq or the REST API, then pipe them into a loop that calls gh issue close or PATCHes each issue's state to closed.