neolabhq/context-engineering-kit

load-issues

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

First seen Apr 23, 2026

Installation

$ npx skills add neolabhq/context-engineering-kit --skill load-issues

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from neolabhq/context-engineering-kit · top by installs.

npx skills add neolabhq/context-engineering-kit

Browse all from neolabhq/context-engineering-kit

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1.7K
License LICENSE
Default branch master
Open issues 6
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,474 B
  • docs SUMMARY.md 83 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1,000 installs

SKILL.md

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

  1. 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

  1. Create the issues directory:

- Run mkdir -p ./specs/issues to ensure the directory exists

  1. 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

  1. 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">
  1. 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.