skills.rest
NeoLabHQ
NeoLabHQOFFICIAL
Explore all skills by this author →
WebsiteGitHub

load-issues

Loads open GitHub issues and saves them as markdown files.

1.5k|154|Updated Nov 13, 2025
Search Tags:#issues#Markdown#Automation#gh CLI#gitHub#spec-Driven Development#Export
One-click install
npx skills add https://github.com/NeoLabHQ/context-engineering-kit --skill load-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: load-issues
Source: https://github.com/NeoLabHQ/context-engineering-kit/tree/main/plugins/git/skills/load-issues
Command: npx skills add https://github.com/NeoLabHQ/context-engineering-kit --skill load-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually copying GitHub issues into local files for planning or documentation is tedious and error-prone. This Skill automates the export of all open issues from a repository into structured markdown files.

Core Features & Use Cases

  • Bulk Issue Export: Fetches all open issues via the GitHub CLI with full metadata including author, labels, assignees, and timestamps.
  • Structured Markdown Output: Saves each issue as a consistently formatted markdown file with a padded-number, kebab-case filename in the ./specs/issues/ directory.
  • Use Case: Before starting a sprint, run this Skill to snapshot all open issues locally so agents or developers can reference them offline during spec-driven development.

Quick Start

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

Frequently Asked Questions about 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?▼

Use the gh CLI to list open issues with gh issue list, then fetch each issue's details with gh issue view in JSON format. Save each result as a markdown file containing the title, status, author, labels, and body.

How to fetch GitHub issue metadata with the gh CLI?▼

Run gh issue view <number> --json number,title,body,state,createdAt,updatedAt,author,labels,assignees,url to retrieve structured metadata. The JSON output can be parsed and formatted into any document template.

Does this require the GitHub CLI to be installed?▼

Yes, the GitHub CLI (gh) must be installed and authenticated with access to the target repository. Without gh, the issue listing and detail-fetching commands cannot run.

Can I load closed issues or only open ones?▼

This workflow loads only open issues, since gh issue list defaults to open issues. To include closed issues, you would need to modify the command with the --state all or --state closed flag.

What happens if the specs/issues directory does not exist?▼

The workflow runs mkdir -p ./specs/issues before writing files, so the directory is created automatically if missing. Existing files with the same names would be overwritten.

Related Skills

Explore More Software Engineering Skills→
likec4likec4
5.6k

likec4-gh-pr-triage

Inspect GitHub PR status, review comments, and issue mentions using the gh CLI.

Official
Intermediate
N0K0N0K0

plan-issue

Convert GitHub issue or markdown feature specs into ordered file-level implementation checklists.

Community
Advanced
learnzdevelopmenthublearnzdevelopmenthub
1

dev-ship

Merge approved pull requests into develop and update issue boards.

Community
Advanced
daymadedaymade
1.3k

github-ops

Automate GitHub PRs, issues, repos, and workflows via gh CLI and APIs.

Community
Advanced