git-load-issues

Fetch GitHub repository issues and save them as markdown files.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Gamezar/opencode-cek --skill git-load-issues-gamezar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-load-issues
Source: https://github.com/Gamezar/opencode-cek/tree/main/plugins/git/skills/git-load-issues
Command: npx skills add https://github.com/Gamezar/opencode-cek --skill git-load-issues-gamezar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of fetching open issues from a GitHub repository and saving them as individual markdown files, making them easily accessible and manageable.

Core Features & Use Cases

  • Issue Archiving: Saves all open GitHub issues into a structured format.
  • Metadata Extraction: Captures key details like title, body, status, author, and labels for each issue.
  • Use Case: Before starting a new development sprint, use this Skill to quickly gather all outstanding tasks and bugs from your GitHub repository into local markdown files for review.

Quick Start

Use the gh CLI to list all open issues in the current repository.

Frequently Asked Questions about git-load-issues

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

FAQPage Schema
How do I export GitHub issues to markdown files for local review?

You can export GitHub issues to markdown by fetching all open issues from a repository and saving them as individual files. This process captures the number, title, body, state, author, labels, and assignees into structured markdown.

Do I need the gh CLI installed to download repository issues as markdown?

Yes, you need the gh CLI installed and authenticated. The Skill relies on the GitHub CLI to query repositories and extract detailed issue data including timestamps, author information, and labels for local archiving.

What is the best way to archive open GitHub issues before a development sprint?

The best way to archive open GitHub issues before a sprint is to fetch all open issues and save them as individual markdown files. This creates a local directory of structured task data for quick offline review.

Does this issue extraction method support GitHub labels and assignees metadata?

Yes, the issue extraction supports detailed metadata. It captures key details like title, body, status, author, labels, assignees, and URLs for each issue, organizing them into a dedicated specs directory.

How are the downloaded GitHub issue markdown files organized on my local machine?

Downloaded GitHub issue markdown files are organized into a ./specs/issues/ directory. The files use a specific naming convention based on issue data, ensuring easy retrieval and structured review of outstanding tasks.