load-issues
SkillFiles & storageLoad all open issues from GitHub and save them as markdown files
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the load-issues skill
What this skill tells your AI
The instructions your AI receives, as published by neolabhq/context-engineering-kit in skills/load-issues/SKILL.md and read by ahel’s review.
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 100to get all open issues
- Run
-
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
- Run
-
Create the issues directory:
- Run
mkdir -p ./specs/issuesto ensure the directory exists
- Run
-
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
- File naming pattern:
-
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">
- 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.
Signals
- GitHub stars
- 2k
- Forks
- 157
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
load-issues- Source
- github.com/neolabhq/context-engineering-kit