fetch-github-issues

Fetch GitHub issues via gh CLI and return oldest 10 or specific issue details.

1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/taiga-K/awesome-backend-template --skill fetch-github-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fetch-github-issues
Source: https://github.com/taiga-K/awesome-backend-template/tree/main/.cursor/skills/fetch-github-issues
Command: npx skills add https://github.com/taiga-K/awesome-backend-template --skill fetch-github-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHubのIssueを効率的に取得・閲覧する作業を自動化します。指定がない場合は最も古い10件を一覧表示し、番号やURLが指定された場合はそのIssueの詳細を取得します。

Core Features & Use Cases

  • Issueの一覧表示: 最も古い10件を一覧表示します。
  • Issueの詳細取得: 指定した番号またはURLのIssueを詳細化します。
  • 自動化ワークフロー: gh CLI経由で他のツールと組み合わせて運用します。

Quick Start

Use the fetch-github-issues skill to retrieve issues from a GitHub repository via gh CLI.

Frequently Asked Questions about fetch-github-issues

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

FAQPage Schema
How do I fetch GitHub issues using the gh CLI for issue tracking automation?

You can fetch GitHub issues using the gh CLI to retrieve the oldest 10 issues by default, or get specific issue details by providing an issue number or URL for your project monitoring workflows.

Can I retrieve a specific GitHub issue by number or URL?

Yes, you can retrieve a specific GitHub issue by providing its issue number or URL. The skill fetches the exact issue details rather than the default list of the oldest 10 open issues.

Do I need gh CLI installed to fetch GitHub issues for triage workflows?

Yes, you need the gh CLI installed and access to the target repository. These prerequisites allow the skill to authenticate and retrieve deterministic issue data for your triage workflows.

What is the best way to list the oldest GitHub issues for automated monitoring?

The best way to list the oldest GitHub issues is to fetch them without specifying an issue number. This returns the oldest 10 issues, providing deterministic results suitable for downstream automation.

How does fetch-github-issues return data for downstream automation pipelines?

The fetch-github-issues skill returns deterministic results with basic input validation. This ensures consistent issue data output that can be reliably parsed and consumed by downstream automation pipelines.

Are there limitations when using gh CLI to fetch issues for large repositories?

When using gh CLI to fetch issues, the default behavior returns only the oldest 10 issues. You must specify individual issue numbers or URLs to retrieve details beyond this default list.