/load-issues
Load all open issues from GitHub and save them as markdown files
Claude Code
$ npx -y skills add NeoLabHQ/context-engineering-kit --skill load-issues --agent claude-code
Codex
$ npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -a codex -y
Cursor
$ npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -a cursor -y
Gemini CLI
$ npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -a gemini-cli -y
GitHub Copilot
$ npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -a github-copilot -y
OpenCode
$ npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -a opencode -y
Windsurf
$ npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -a windsurf -y
SKILL.md
load-issues.SKILL.mdname: load-issues
description: Load all open issues from GitHub and save them as markdown 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 100` to 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/issues` to 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.
Read more
name: load-issues description: Load all open issues from GitHub and save them as markdown 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 100` to 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/issues` to 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.
A hand-crafted collection of advanced context engineering techniques and patterns with minimal token footprint, focused on improving agent result quality and predictability.
Other skills on context-engineering-kit.
add-task
creates draft task file in .specs/tasks/draft/ with original user intent
agent-evaluation
Evaluate and improve Claude Code commands, skills, and agents. Use when testing prompt effectiveness, validating context…
analyse-problem
Comprehensive A3 one-page problem analysis with root cause and action plan
analyse
Auto-selects best Kaizen method (Gemba Walk, Value Stream, or Muda) for target
analyze-issue
Analyze a GitHub issue and create a detailed technical specification
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about load-issues.
- Which coding agents can use load-issues?
- load-issues installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

