fetch-github-issue

Fetch GitHub issue details by ID and save them as structured markdown files.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/ductrung-nguyen/Orca-vscode --skill fetch-github-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fetch-github-issue
Source: https://github.com/ductrung-nguyen/Orca-vscode/tree/main/.github/skills/fetch-github-issue
Command: npx skills add https://github.com/ductrung-nguyen/Orca-vscode --skill fetch-github-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of retrieving GitHub issue details and converting them into structured markdown files, streamlining the integration of issues into development pipelines.

Core Features & Use Cases

  • Issue Retrieval: Fetches issue title, body, labels, assignees, and other metadata by issue ID.
  • Structured Output: Saves fetched issue content into a standardized markdown format for easy consumption by other tools.
  • Pipeline Integration: Designed to seamlessly feed GitHub issue data into development workflows, requirement documents, or PRD generation.

Quick Start

Use the fetch-github-issue skill to get issue number 123 from the current repository.

Frequently Asked Questions about fetch-github-issue

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

FAQPage Schema
How do I fetch GitHub issue details and save them as a markdown file?

To fetch GitHub issue details and save them as a markdown file, this Skill retrieves issue title, body, labels, and assignees by ID, converting the data into a structured markdown format for pipeline consumption.

Do I need GitHub CLI installed to fetch issues into my development workflow?

Yes, fetching GitHub issues into your development workflow requires the GitHub CLI (`gh`) to be installed and authenticated in your environment to access repository data.

Can I convert a GitHub issue into a requirements document automatically?

You can convert a GitHub issue into a requirements document automatically by fetching the issue metadata and body, which is then output as a structured markdown file ready for PRD generation.

What is the best way to integrate GitHub issues into an idea-to-software pipeline?

Integrating GitHub issues into an idea-to-software pipeline is done by fetching issue content by ID and saving it as a standardized markdown file, seamlessly feeding the issue data into downstream development workflows.

What GitHub issue metadata is retrieved when fetching issues for a requirements document?

When fetching GitHub issues for a requirements document, the retrieved metadata includes the issue title, body, labels, assignees, and other relevant repository details structured into markdown.

Why is my GitHub issue fetch not working in the development pipeline?

Your GitHub issue fetch might not be working because the GitHub CLI (`gh`) is not installed or properly authenticated, which is required to retrieve issue details from the repository.