/load-issues
Load all open issues from GitHub and save them as markdown files
$ npx -y skills add NeoLabHQ/context-engineering-kit --skill load-issues --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/load-issues
Context preview
The summary Claude sees to decide when to auto-load this skill.
Load all open issues from GitHub and save them as markdown files
SKILL.md
load-issues.SKILL.mdname: 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:
# 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.
Read more
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:
# 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.
A hand-crafted collection of advanced context engineering techniques and patterns with minimal token footprint, focused on improving agent result quality and predictability.
Repo: NeoLabHQ/context-engineering-kit
Other skills on context-engineering-kit.
- /agent-evaluation
Evaluate and improve Claude Code commands, skills, and agents. Use when testing prompt effectiveness, validating context engineering choices, or measuring improvement quality.
Open skill - /apply-anthropic-skill-best-practices
Comprehensive guide for skill development based on Anthropic's official best practices - use for complex skills requiring detailed structure
Open skill - /context-engineering
Understand the components, mechanics, and constraints of context in agent systems. Use when writing, editing, or optimizing commands, skills, or sub-agents prompts.
Open skill - /create-agent
Comprehensive guide for creating Claude Code agents with proper structure, triggering conditions, system prompts, and validation - combines official Anthropic best practices with proven patterns
Open skill - /create-command
Interactive assistant for creating new Claude commands with proper structure, patterns, and MCP tool integration
Open skill - /create-hook
Create and configure git hooks with intelligent project analysis, suggestions, and automated testing
Open skill