issue-workflow

Automating GitHub issue workflows involves coordinating start, checkpoint, and finish phases tied to specific issues to ensure traceable progress. This Skill standardizes issue-driven project work by enforcing issue references in commits and managing structured progress updates across individual issues or related sub-issues.

Enforcing issue references in commit messages is handled automatically during the commit and finish phases of issue-driven work. This ensures traceable progress by linking structured commits directly to their corresponding GitHub issues or formal parent-child sub-issues.

Managing parent-child sub-issues in GitHub is supported by creating formal relationships for large tasks during the issue-driven workflow. This Skill provides guidance for linking issues, updating descriptions, and coordinating progress updates across related sub-issues.

Yes, creating or linking issues via `gh` is supported to initiate and track workflow phases. The GitHub CLI is utilized to apply mode-specific behavior with safety checks, ensuring clear guidance for starting, checkpointing, and finishing issue-driven work.

Updating issue descriptions and closing work upon completion is supported through the finish mode of the issue-driven workflow. This ensures formal closure of GitHub issues by applying safety checks and coordinating delivery milestones across the tracked tasks.

To start tracking work, you invoke the issue-start phase with an issue key and optional context. This begins the issue-driven workflow, applying mode-specific behavior and safety checks to coordinate structured commits and progress updates for that issue.