orchestrator:fetch-issue

Fetch and validate open GitHub issues with non-empty descriptions using GitHub CLI and jq.

Updated Feb 24, 2026

Search Tags:#automation #workflow #github #validation #cli #issue

Ready to run

npx skills add https://github.com/atournayre/claude-personas --skill orchestrator-fetch-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: orchestrator:fetch-issue
Source: https://github.com/atournayre/claude-personas/tree/main/orchestrator/skills/fetch-issue
Command: npx skills add https://github.com/atournayre/claude-personas --skill orchestrator-fetch-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the retrieval and validation of GitHub issue details, ensuring that only valid, open issues with descriptions are processed for automated workflows.

Core Features & Use Cases

Issue Retrieval: Fetches issue title, body, labels, and state using the GitHub CLI.
Validation: Checks if the issue is 'OPEN' and has a non-empty description.
Workflow State Management: Saves fetched issue data into a structured workflow state file for subsequent processing.
Use Case: Before starting a new development task based on a GitHub issue, use this skill to ensure the issue is ready for processing, preventing wasted effort on invalid or incomplete tasks.

Quick Start

Use the orchestrator:fetch-issue skill to fetch and validate issue number 123.

Frequently Asked Questions about orchestrator:fetch-issue

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

FAQPage Schema

How do I fetch and validate GitHub issues for automated workflows?▼

To fetch and validate GitHub issues, use this skill to retrieve issue details via the GitHub CLI and parse data with jq. It verifies the issue is in an OPEN state and has a non-empty description before saving validated details into a workflow state file.

What validation checks are performed on GitHub issue content before processing?▼

GitHub issue validation checks if the issue state is OPEN and if the description body is non-empty. This ensures automated workflows only process valid, open issues with descriptions, preventing wasted effort on incomplete tasks.

Do I need the GitHub CLI and jq to retrieve issue details in an automated workflow?▼

Yes, retrieving issue details requires the GitHub CLI to fetch title, body, labels, and state, while jq handles data parsing. These dependencies extract and validate issue data for downstream workflow state management.

Can I save fetched GitHub issue data into a structured workflow state file?▼

Yes, fetched GitHub issue data is saved into a structured workflow state file. After validating the issue is open and has a description, the skill stores the extracted title, body, and labels for subsequent processing steps.

When should I not use automated GitHub issue validation in my workflow?▼

You should not use automated GitHub issue validation if your task does not depend on issue state or content completeness. It specifically filters out closed issues or issues with empty descriptions, halting if validation fails.

What GitHub issue data is retrieved for automated task processing?▼

Retrieved GitHub issue data includes the issue title, body, labels, and state. This content is extracted using the GitHub CLI and parsed with jq to ensure automated workflows have valid issue details for processing.