# Load Issues

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

- Repository: https://github.com/NeoLabHQ/context-engineering-kit (1797 stars)
- Category: Git and review
- License: GPL-3.0
- Last updated: 2026-08-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -g -a claude-code -y`
Codex: `npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -g -a codex -y`
Cursor: `npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -g -a cursor -y`
Gemini CLI: `npx skills add NeoLabHQ/context-engineering-kit --skill load-issues -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add NeoLabHQ/context-engineering-kit`

## Description

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

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

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:

```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">
```

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.