Best use case
git:load-issues is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Load all open issues from GitHub and save them as markdown files
Teams using git:load-issues should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/load-issues/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How git:load-issues Compares
| Feature / Agent | git:load-issues | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Load all open issues from GitHub and save them as markdown files
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
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
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
sdd:plan
Refine, parallelize, and verify a draft task specification into a fully planned implementation-ready task
sdd:implement
Implement a task with automated LLM-as-Judge verification for critical steps
sdd:create-ideas
Generate ideas in one shot using creative sampling
sdd:brainstorm
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
sdd:add-task
creates draft task file in .specs/tasks/draft/ with original user intent
sadd:tree-of-thoughts
Execute tasks through systematic exploration, pruning, and expansion using Tree of Thoughts methodology with meta-judge evaluation specifications and multi-agent evaluation
sadd:subagent-driven-development
Use when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or dependencies - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates
sadd:multi-agent-patterns
Design multi-agent architectures for complex tasks. Use when single-agent context limits are exceeded, when tasks decompose naturally into subtasks, or when specializing agents improves quality.