load-issues

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

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "load-issues" with this command: npx skills add glennguilloux/context-engineering-kit/glennguilloux-context-engineering-kit-load-issues

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.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

subagent-driven-development

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

setup-code-formating

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

setup-codemap-cli

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

test-driven-development

No summary provided by upstream source.

Repository SourceNeeds Review