Load Issues
- 851 installs
- 1.3k repo stars
- Updated July 26, 2026
- neolabhq/context-engineering-kit
load-issues is a Claude Code skill that uses the GitHub CLI to pull every open repository issue into structured markdown files for developers who need offline, agent-readable backlog context for review and planning.
About
load-issues is a context-engineering-kit skill that automates GitHub issue export for agent-assisted planning. The workflow runs `gh issue list --limit 100`, then fetches each open issue with `gh issue view` JSON fields including number, title, body, state, labels, assignees, author, and URL. Each issue is saved as a markdown file in `./specs/issues/`, giving developers a local, searchable spec corpus without manual copy-paste. Reach for load-issues when you want Claude or another coding agent to triage backlog items, draft implementation plans, or cross-reference open work against in-repo specs. The skill requires Bash access for `gh issue:*`, `mkdir`, and Write permissions, and assumes the current directory is a GitHub repository with gh authenticated.
- Automatically loads all open GitHub issues using the gh CLI
- Fetches full metadata including labels, assignees, and timestamps
- Saves each issue as a padded, kebab-case markdown file in ./specs/issues/
- Applies a consistent markdown template with Status, Description, Labels, and Assignees sections
- Ends with a summary report of total issues and created files
Load Issues by the numbers
- 851 all-time installs (skills.sh)
- +47 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #549 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/neolabhq/context-engineering-kit --skill load-issuesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 851 |
|---|---|
| repo stars | ★ 1.3k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 26, 2026 |
| Repository | neolabhq/context-engineering-kit ↗ |
How do you export GitHub issues to markdown?
Pull every open GitHub issue into structured markdown files for review and planning.
Who is it for?
Developers using gh CLI who want agent-readable local copies of open GitHub backlog items for planning sessions.
Skip if: Teams without GitHub issues, repositories where gh is not authenticated, or workflows that need closed-issue history beyond the open-issue export.
When should I use this skill?
A developer asks to pull, sync, or review open GitHub issues as local markdown specs before planning or implementation.
What you get
Markdown issue files in ./specs/issues/ with titles, bodies, labels, assignees, and metadata.
- ./specs/issues/*.md issue files
By the numbers
- Exports up to 100 open issues per run via `gh issue list --limit 100`
- Writes issue markdown files to `./specs/issues/`
Files
Load all open issues from the current GitHub repository and save them as markdown files in the ./specs/issues/ directory.
Follow these steps:
1. Use the gh CLI to list all open issues in the current repository:
- Run
gh issue list --limit 100to get all open issues
2. 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
3. Create the issues directory:
- Run
mkdir -p ./specs/issuesto ensure the directory exists
4. 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
5. Use the following markdown template for each issue file:
# 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">6. 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.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kHow it compares
Choose load-issues over manual issue copy-paste when you need repeatable, structured markdown exports for agent context rather than one-off issue lookups.
FAQ
Where does load-issues save exported issues?
load-issues saves each open GitHub issue as a markdown file in the `./specs/issues/` directory of the current repository, created with mkdir if needed.
What gh command does load-issues use to list issues?
load-issues runs `gh issue list --limit 100` on the current repository, then calls `gh issue view <number> --json` for detailed fields on each open issue.
Is Load Issues safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.