issue-workflow

Fetch GitHub issues by number and orchestrate grooming, implementation, review, and QA pipelines.

81|31|Updated Jul 12, 2016
One-click install
npx skills add https://github.com/wp-media/imagify-plugin --skill issue-workflow-wp-media
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-workflow
Source: https://github.com/wp-media/imagify-plugin/tree/main/.claude/skills/issue-workflow
Command: npx skills add https://github.com/wp-media/imagify-plugin --skill issue-workflow-wp-media

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, git, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the end-to-end lifecycle of handling a GitHub issue: from extraction and context gathering to grooming, implementation, review, and QA orchestration, reducing manual handoffs and speeding up delivery.

Core Features & Use Cases

  • Orchestrates issue intake: fetch by number, derive context from related epics, sub-issues, and task lists, and prepare downstream work items.
  • Coordinates deterministic task execution: creates branches, drafts PRs, and scripts-driven steps via an inline orchestrator, ensuring reproducible workflows.
  • Supports complex project structures: comprehends parent epics, sub-issues, and project-type signals to guide triage and task assignment.

Quick Start

Fetch the issue by its number and trigger the end-to-end grooming → implementation → review → QA pipeline.

Frequently Asked Questions about issue-workflow

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

FAQPage Schema
How do I automate GitHub issue grooming from intake to QA?

Automate GitHub issue grooming by fetching an issue by number and driving the full pipeline through implementation, review, and QA. The workflow coordinates parent Epics, sub-issues, and related issues while creating branches and drafting PRs inline.

How does issue grooming coordinate parent Epics and sub-issues in GitHub?

Issue grooming coordinates parent Epics and sub-issues by extracting context from related issues and task lists. It comprehends project-type signals to guide triage, task assignment, and downstream work item preparation.

Do I need gh and jq installed to automate my GitHub issue workflow?

Yes, you need gh, jq, and git installed. The inline orchestrator executes deterministic steps via shell commands using these dependencies, ensuring reproducible workflows with explicit base branches and error handling.

What's the best way to ensure deterministic execution when automating GitHub PR drafts?

Ensure deterministic execution by using an inline orchestrator that scripts driven steps via shell commands with explicit base branches. It provides error handling and audit logging to .ai/issues for full traceability of the PR draft creation.

Can I trace automated issue workflow steps back to their original GitHub issue?

Yes, you can trace automated issue workflow steps. The pipeline records audit logs to .ai/issues, providing traceability for every action taken during the grooming, implementation, review, and QA phases of the GitHub issue.

Why does my automated GitHub issue workflow require explicit base branches?

Automated GitHub issue workflows require explicit base branches to ensure deterministic execution. Specifying the base branch prevents ambiguous merges and guarantees reproducible workflows when creating branches and drafting PRs from the issue context.