orchestrator:fetch-issue

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.

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.

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.

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.

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.

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.