Load Issues

NeoLabHQ/context-engineering-kit/skills/load-issues

by NeoLabHQ23e2428e809d77717f8acc9659c374a3a1fcb93eNo licenseListed Oct 9, 2026Updated Oct 9, 2026

Load all open issues from GitHub and save them as markdown files

Instructions onlyProductivity & Workflow

AI-generated overview

Fetches all open GitHub issues from the current repository and saves each as a formatted markdown file.

What it does: The skill lists all open issues in the current GitHub repository using the gh CLI, then retrieves detailed metadata for each issue, including number, title, body, state, dates, author, labels, assignees and URL. It creates a specs/issues directory and writes one markdown file per issue, named with a zero-padded issue number and a kebab-case title. It finishes with a summary of the total issues loaded and the files created.
When to use it: Use it when you want a local, readable snapshot of a repository's open issues as markdown files. It suits exporting issue backlogs into a specs or documentation folder for review or offline reference.
Requirements: Requires the gh CLI installed and authenticated with access to the target GitHub repository, plus network access to GitHub. It ships no scripts; it is instructions only.

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

Follow these steps:

Use the gh CLI to list all open issues in the current repository:
- Run gh issue list --limit 100 to get all open issues
For each open issue, fetch detailed information:
- Run gh issue view <number> --json number,title,body,state,createdAt,updatedAt,author,labels,assignees,url
- Extract all relevant metadata
Create the issues directory:
- Run mkdir -p ./specs/issues to ensure the directory exists
Save each issue as a separate markdown file:
- File naming pattern: <number-padded-to-3-digits>-<kebab-case-title>.md
- Example: 007-make-code-review-trigger-on-sql-sh-changes.md
Use the following markdown template for each issue file:

markdown

# Issue #<number>: <title>
**Status:** <state>**Created:** <createdAt>**Updated:** <updatedAt>**Author:** <author.name> (@<author.login>)**URL:** <url>
## Description
<body>
## Labels
<labels or "None">
## Assignees
<assignees or "None">

# Issue #<number>: <title>
**Status:** <state>**Created:** <createdAt>**Updated:** <updatedAt>**Author:** <author.name> (@<author.login>)**URL:** <url>
## Description
<body>
## Labels
<labels or "None">
## Assignees
<assignees or "None">

After all issues are saved, provide a summary of:
- Total number of issues loaded
- List of created files with their issue numbers and titles

IMPORTANT: Execute all steps in the correct order and ensure all issue data is properly formatted in the markdown files.

Source and attribution

Source:NeoLabHQ/context-engineering-kitinskills/load-issuesat commit23e2428

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Load Issues

Source and attribution

More from NeoLabHQ/context-engineering-kit

Write Tests

Tree Of Thoughts

Write Concisely

Test Prompt

Update Docs

Test Skill

More in Productivity & Workflow

Morning Note

Dd Meeting Prep

Dd Checklist

Deal Tracker

Client Review

Morning Note