← LeaderboardThe Skill Leaderboard

load-issues

Skill file skills/load-issues/SKILL.md in NeoLabHQ/context-engineering-kit. Read the publisher’s upstream source.

Description awaits a fresh source check.

Published by NeoLabHQ ↗NeoLabHQ/context-engineering-kit

Try your first task

load-issues

Start a fresh conversation. Replace the highlighted placeholders.

Use load-issues to load all open issues from [repository] into individual markdown files under specs/issues and return the issue count plus created-file list.

Required inputs

  • [repository]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: load-issuesdescription: 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">
  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.