load-issues
installsforks
How to install load-issues?
neolabhq/context-engineering-kit/load-issues
$npx -y skills add NeoLabHQ/context-engineering-kit --skill load-issuesLoad all open issues from GitHub and save them as markdown files
SKILL.md
| 1 | Load all open issues from the current GitHub repository and save them as markdown files in the `./specs/issues/` directory. |
| 2 | |
| 3 | Follow these steps: |
| 4 | |
| 5 | 1. Use the gh CLI to list all open issues in the current repository: |
| 6 | - Run `gh issue list --limit 100` to get all open issues |
| 7 | |
| 8 | 2. For each open issue, fetch detailed information: |
| 9 | - Run `gh issue view <number> --json number,title,body,state,createdAt,updatedAt,author,labels,assignees,url` |
| 10 | - Extract all relevant metadata |
| 11 | |
| 12 | 3. Create the issues directory: |
| 13 | - Run `mkdir -p ./specs/issues` to ensure the directory exists |
| 14 | |
| 15 | 4. Save each issue as a separate markdown file: |
| 16 | - File naming pattern: `<number-padded-to-3-digits>-<kebab-case-title>.md` |
| 17 | - Example: `007-make-code-review-trigger-on-sql-sh-changes.md` |
| 18 | |
| 19 | 5. Use the following markdown template for each issue file: |
| 20 | |
| 21 | ```markdown |
| 22 | # Issue #<number>: <title> |
| 23 | |
| 24 | **Status:** <state> |
| 25 | **Created:** <createdAt> |
| 26 | **Updated:** <updatedAt> |
| 27 | **Author:** <author.name> (@<author.login>) |
| 28 | **URL:** <url> |
| 29 | |
| 30 | ## Description |
| 31 | |
| 32 | <body> |
| 33 | |
| 34 | ## Labels |
| 35 | |
| 36 | <labels or "None"> |
| 37 | |
| 38 | ## Assignees |
| 39 | |
| 40 | <assignees or "None"> |
| 41 | ``` |
| 42 | |
| 43 | 6. After all issues are saved, provide a summary of: |
| 44 | - Total number of issues loaded |
| 45 | - List of created files with their issue numbers and titles |
| 46 | |
| 47 | IMPORTANT: Execute all steps in the correct order and ensure all issue data is properly formatted in the markdown files. |
People who liked this also viewed
6 picksType
- caveman-commitUltra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. UsSkillsJul 2026
- git-guardrails-claude-codeSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- setup-pre-commitSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- resolving-merge-conflictsSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- using-git-worktreesUse 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 fallbackSkillsJul 2026
- finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanupSkillsJul 2026
