gh-issues

Manage GitHub Issues via gh CLI with JSON and jq scripting.

215|26|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/serejaris/ris-claude-code --skill gh-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issues
Source: https://github.com/serejaris/ris-claude-code/tree/main/skills/gh-issues
Command: npx skills add https://github.com/serejaris/ris-claude-code --skill gh-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing GitHub issues via the web UI is slow, and AI context often gets lost between sessions. This Skill enables fast, CLI-driven issue management and stores AI session context directly in issue comments for seamless handoffs.

Core Features & Use Cases

  • Full gh issue CLI reference with JSON/jq patterns for scripting.
  • Bulk operations and advanced search filters to triage and manage multiple issues at once.
  • AI session context storage — save/load work state directly in issue comments for continuity.
  • Issue lifecycle workflows (backlog → in-progress → done) and an issue→branch→PR pattern.

Quick Start

Use the gh-issues Skill by installing it into Claude's skill path: cp -r skills/gh-issues ~/.claude/skills/ Then activate the skill and issue your first task, e.g.: gh issue create -t "Sample task" -b "Describe the task" -l task For quick hands-on, you can load active issues with: gh issue list -s open

Frequently Asked Questions about gh-issues

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

FAQPage Schema
How do I manage GitHub Issues from the CLI without losing AI session context?

You can manage GitHub Issues from the CLI by using gh commands to create, search, and update issues, while storing AI session context directly in issue comments to preserve work state across sessions.

Can I perform bulk operations on GitHub Issues using the gh CLI?

Yes, you can perform bulk operations on GitHub Issues by leveraging advanced search filters and JSON outputs with jq, allowing you to triage and update multiple issues at once through scriptable CLI patterns.

How do I automate an issue to branch to PR workflow on GitHub?

You can automate an issue to branch to PR workflow by following the issue lifecycle pattern from backlog to in-progress to done, using gh CLI commands to link issues to branches and pull requests for streamlined task tracking.

Do I need a GitHub account and gh CLI installed to script GitHub Issues management?

Yes, you need both the gh CLI installed and a GitHub account authenticated, because the workflow interfaces directly with the gh CLI and assumes read and write access to repository data for issue management.

What is the best way to script GitHub Issues searches for triage?

The best way to script GitHub Issues searches for triage is using gh CLI search filters combined with jq, which parses JSON outputs to extract specific issue fields for automated processing and bulk updates.

Why does managing GitHub Issues via the web UI slow down development?

Managing GitHub Issues via the web UI slows development because it requires manual context switching, whereas a CLI-driven approach with AI context stored in comments enables fast, scriptable issue management and seamless session handoffs.