gh-fetch-issues

Fetch open GitHub issues and exclude on-hold or in-progress labels.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/smallorbit/smallorbit-plugins --skill gh-fetch-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-fetch-issues
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/plugins/swarmkit/skills/gh-fetch-issues
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill gh-fetch-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the process of locating and filtering GitHub issues for swarm workflows by automatically collecting open issues and excluding blocked work items.

Core Features & Use Cases

  • Issue retrieval: fetch open issues with key fields such as number, title, body, and labels.
  • Label-based filtering: automatically exclude issues labeled on-hold or status:in-progress.
  • Use Case: during planning sprints, surface only actionable issues for assignment and triage.

Quick Start

Run the command to fetch the first 50 open issues and filter out those labeled on-hold or status:in-progress.

Frequently Asked Questions about gh-fetch-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fetch open GitHub issues and filter out blocked work items for sprint planning?

To fetch open GitHub issues and filter blocked work items, this skill queries issues via the GitHub CLI or API and automatically excludes items labeled on-hold or status:in-progress. It surfaces only actionable tasks for sprint planning and triage.

Can I use GitHub labels to exclude in-progress issues from swarm planning workflows?

Yes, you can use GitHub labels to exclude in-progress issues from swarm planning. The skill applies label-based filtering to automatically remove issues tagged on-hold or status:in-progress from the fetched results.

Do I need the GitHub CLI to retrieve and triage open issues across multiple repositories?

Yes, you need the GitHub CLI or API access to retrieve and triage open issues across multiple repositories. The skill requires this access to query issues and apply the label-based filters that surface actionable work items.

What GitHub issue fields are retrieved when filtering actionable work items?

When filtering actionable work items, the skill retrieves key GitHub issue fields including the issue number, title, body, and labels. This provides the necessary context for assignment and triage during swarm workflows.

How many open GitHub issues can I fetch and filter at once for triage?

You can fetch and filter the first 50 open GitHub issues at once for triage. The quick start command retrieves these issues and automatically filters out those labeled on-hold or status:in-progress.