> git:load-issues
Load all open issues from GitHub and save them as markdown files
curl "https://skillshub.wtf/NeoLabHQ/context-engineering-kit/load-issues?format=md"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 --same-repo
> tech-stack:add-typescript-best-practices
Setup TypeScript best practices and code style rules in CLAUDE.md
> tdd:write-tests
Systematically add test coverage for all local code changes using specialized review and development agents. Add tests for uncommitted changes (including untracked files), or if everything is commited, then will cover latest commit.
> tdd:test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
> tdd:fix-tests
Systematically fix all failing tests after business logic changes or refactoring