github-issues

Triage GitHub issues via gh CLI or authenticated curl requests.

641|104|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/loongclaw-ai/loongclaw --skill github-issues-loongclaw-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/loongclaw-ai/loongclaw/tree/main/skills/github-issues
Command: npx skills add https://github.com/loongclaw-ai/loongclaw --skill github-issues-loongclaw-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes the tedium of juggling GitHub issue commands across CLI and API clients by providing a unified workflow for viewing, creating, triaging, labeling, and linking issues while gracefully falling back to REST calls when gh is unavailable.

Core Features & Use Cases

  • Dual auth modes: prefer the gh CLI when authenticated, otherwise reuse tokens with curl so the skill runs reliably across environments.
  • Complete issue lifecycle: list, view, create, label, assign, comment, close, reopen, and link issues to pull requests, plus templates for consistent bug and feature reports.
  • Use Case: Triage a sprint by listing needs-triage issues, applying priority labels, assigning owners, and documenting context with the provided templates.

Quick Start

Ask to triage open GitHub issues by listing all needs-triage items and marking them with priority labels.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I triage GitHub issues using the command line?

To triage GitHub issues via command line, you can list open items, apply priority labels, assign owners, and add comments using either the gh CLI or authenticated curl requests. This streamlines sprint maintenance workflows directly from your terminal.

Can I manage GitHub issues with curl if the gh CLI is not installed?

Yes, you can manage GitHub issues with curl if the gh CLI is unavailable. The skill gracefully falls back to REST calls using authenticated tokens, allowing you to reliably view, create, and update issue lifecycles across different environments.

What is the best way to link a GitHub issue to a pull request?

The best way to link a GitHub issue to a pull request is by using CLI or REST commands that support issue lifecycle management. You can connect issues to PRs directly during your triage workflow to maintain traceability.

How do I bulk update issue statuses and labels in GitHub?

You can bulk update issue statuses and labels by executing commands that support bulk operations within your repository. The skill enables applying labels, changing assignees, and updating statuses across multiple issues efficiently.

Do I need authenticated GitHub access to create issues from the terminal?

Yes, authenticated GitHub access is required to create issues from the terminal. The skill needs proper authentication to detect repository remotes and execute actions like viewing, creating, or modifying issues via gh CLI or curl.

Why use CLI for GitHub issue tracking instead of the web interface?

Using CLI for GitHub issue tracking removes the tedium of juggling commands across clients and provides a unified workflow. It enables rapid triage, consistent bug reports via templates, and seamless linking to PRs without leaving the terminal.