NeoLabHQ/load-issues
plugins/git/skills/load-issues/SKILL.md
Load all open issues from GitHub and save them as markdown files
$ install --global
skillsauthnpx skillsauth add NeoLabHQ/context-engineering-kit load-issuesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Error
VirusTotalMulti-engine malware detection
70%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 6:48 AM12.2s1 file scanned
SKILL.md
- 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:
-
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.
Related Skills
NeoLabHQ/write-tests
development
VerifiedTrustedOfficial
Add missing test coverage for your local code changes by generating new test files (covers uncommitted and untracked changes, or the latest commit if everything is committed). Use when you want write tests for new logic or increase test coverage.
1,412SKILL.mdUpdated Aug 27, 2026
NeoLabHQ/write-concisely
testing
VerifiedTrustedOfficial
Apply writing rules to any documentation that humans will read. Makes your writing clearer, stronger, and more professional.
1,412SKILL.mdUpdated Aug 27, 2026
NeoLabHQ/why
research
VerifiedTrustedOfficial
Iterative Five Whys root cause analysis drilling from symptoms to fundamentals
1,412SKILL.mdUpdated Aug 27, 2026
NeoLabHQ/update-docs
development
VerifiedTrustedOfficial
Update and maintain project documentation for local code changes using multi-agent workflow with tech-writer agents. Covers docs/, READMEs, JSDoc, and API documentation.
1,412SKILL.mdUpdated Aug 27, 2026