NeoLabHQ/context-engineering-kit / plugins/git/skills/load-issues
load-issues
VerifiedLoad all open issues from GitHub and save them as markdown files
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.6 KB |
SKILL.md
View on GitHub---
name: load-issues
description: Load all open issues from GitHub and save them as markdown files
argument-hint: None required - loads all open issues automatically
allowed-tools: Bash(gh issue:*), Bash(mkdir:*), Write
---
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:
```markdown
# 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">
```
6. 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |