explainx.ainewsletter3.02k
Productivity

git:load-issues▌

neolabhq/context-engineering-kit · updated Apr 8, 2026

$npx skills add https://github.com/neolabhq/context-engineering-kit --skill git:load-issues
0 commentsdiscussion
summary

Load all open issues from the current GitHub repository and save them as markdown files in the ./specs/issues/ directory.

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

  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.

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.7★★★★★29 reviews
  • ★★★★★Ganesh Mohane· Dec 20, 2024

    git:load-issues has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Sophia Robinson· Dec 16, 2024

    git:load-issues reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • ★★★★★Rahul Santra· Nov 11, 2024

    Keeps context tight: git:load-issues is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • ★★★★★Pratham Ware· Oct 2, 2024

    We added git:load-issues from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Xiao Rao· Sep 25, 2024

    Keeps context tight: git:load-issues is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • ★★★★★Piyush G· Sep 9, 2024

    Useful defaults in git:load-issues — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Aisha Shah· Sep 9, 2024

    We added git:load-issues from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Tariq Lopez· Aug 28, 2024

    Keeps context tight: git:load-issues is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • ★★★★★Xiao Gill· Aug 16, 2024

    We added git:load-issues from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Sakshi Patil· Jul 27, 2024

    git:load-issues reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 29

1 / 3