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:
-
Use the gh CLI to list all open issues in the current repository:
- Run
gh issue list --limit 100to get all open issues
- Run
-
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
- Run
-
Create the issues directory:
- Run
mkdir -p ./specs/issuesto ensure the directory exists
- Run
-
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
- File naming pattern:
-
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">
- 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.
More from glennguilloux/context-engineering-kit
setup-serena-mcp
Guide for setup Serena MCP server for semantic code retrieval and editing capabilities
9tree-of-thoughts
Execute tasks through systematic exploration, pruning, and expansion using Tree of Thoughts methodology with multi-agent evaluation
6write-concisely
Apply writing rules to any documentation that humans will read. Makes your writing clearer, stronger, and more professional.
4setup-arxiv-mcp
Guide for setup arXiv paper search MCP server using Docker MCP
4analyse
Auto-selects best Kaizen method (Gemba Walk, Value Stream, or Muda) for target
3setup-code-formating
Sets up code formatting rules and style guidelines in CLAUDE.md
3