git:load-issues

Load open GitHub issues and save each as a markdown file.

Updated Mar 4, 2026

Search Tags:#automation #git #templates #markdown #github #issues #file-naming

Ready to run

npx skills add https://github.com/dalawwa/labor-methods --skill git-load-issues

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git:load-issues
Source: https://github.com/dalawwa/labor-methods/tree/main/.cek/plugins/git/skills/load-issues
Command: npx skills add https://github.com/dalawwa/labor-methods --skill git-load-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Load all open issues from the current GitHub repository and save them as markdown files in the ./specs/issues/ directory.

Core Features & Use Cases

List all open issues in the repository using the gh CLI and fetch detailed information for each issue (number, title, body, state, createdAt, updatedAt, author, labels, assignees, url).
Create the specs/issues directory if it does not exist and save each issue as a separate markdown file named with a three-digit padded number and a kebab-case title, following a consistent template.
Provide a standardized template per issue including status, timestamps, author, URL, description, labels, and assignees for easy archival and review.

Quick Start

Run the skill to list all open issues with gh, generate a markdown file per issue in ./specs/issues, and save them with the standardized filename format.

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 all open GitHub issues to markdown files?▼

You can export all open GitHub issues to markdown files by running the skill to list all issues via gh CLI and save each one as a separate markdown file in the ./specs/issues directory. It uses a standardized template for consistent formatting.

What format are GitHub issues saved as when exported to markdown?▼

GitHub issues are saved as markdown files using a three-digit padded issue number and a kebab-case title for the filename. The content includes a standardized template with status, timestamps, author, URL, description, labels, and assignees.

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

Yes, the skill uses the gh CLI to list all open issues in the repository and fetch detailed metadata for each one, including number, title, body, state, timestamps, author, labels, assignees, and URL for markdown file generation.

Can I automatically create the specs directory when saving GitHub issues?▼

Yes, the skill automatically creates the ./specs/issues directory if it does not exist before saving the exported GitHub issues as individual markdown files. This ensures deterministic file creation and organization.

What is the best way to archive GitHub issues for offline review?▼

The best way to archive GitHub issues for offline review is to export them as standardized markdown files. This skill fetches all open issues with their full metadata and saves them locally using a consistent per-issue template for easy archival.

Does this approach work with repositories that have many open issues?▼

Yes, this approach is designed for repositories with many open issues. It automates loading all open issues from the current GitHub repository and systematically saves them as organized markdown files.