mav-github-issue-workflow

Automate GitHub issue interactions with state tracking and PR coordination.

10|2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/thermiteau/maverick --skill mav-github-issue-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mav-github-issue-workflow
Source: https://github.com/thermiteau/maverick/tree/main/skills/mav-github-issue-workflow
Command: npx skills add https://github.com/thermiteau/maverick --skill mav-github-issue-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides reusable patterns for interacting with GitHub issues, including reading, commenting, updating, and state tracking, so teams can maintain consistent issue lifecycles across sessions and agents.

Core Features & Use Cases

  • Stateful issue workflow: maintains a local state file at .claude/issue-state.json to track progress across sessions and agents.
  • Reading and posting: reads issue data via gh and posts comments for design, plan, and completion with captured IDs for updates.
  • Branching and PR guidance: coordinates branch creation and PR generation in line with the mav-git-workflow rules to close issues automatically when merged.
  • Resilience and traceability: provides deterministic prompts and a recoverable workflow to resume work after interruptions.

Quick Start

Initialize and track an issue's lifecycle across sessions using mav-github-issue-workflow.

Frequently Asked Questions about mav-github-issue-workflow

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

FAQPage Schema
How do I track GitHub issue state across multiple sessions?

Track GitHub issue state across multiple sessions by maintaining a local state file at .claude/issue-state.json, which records progress and captured comment IDs to resume workflows after interruptions.

How do I automate GitHub issue comments through the lifecycle?

Automate GitHub issue comments by reading issue data with the gh CLI and posting deterministic comments for design, plan, and completion phases, capturing IDs for later updates.

Can I coordinate branch creation and pull requests with GitHub issue tracking?

Coordinate branch creation and pull requests with issue tracking by following git workflow rules to generate PRs that automatically close the associated issues upon merging.

What is the best way to manage design, plan, and completion phases for GitHub issues?

Manage design, plan, and completion phases for GitHub issues using deterministic prompts and a recoverable workflow that applies consistent state tracking and PR coordination rules.

Do I need GitHub CLI and jq to automate issue workflows?

GitHub CLI and jq are required to perform data operations for issue workflows, enabling reading issue data and managing state transitions deterministically.

Why does my GitHub issue workflow lose progress after an interruption?

Issue workflows lose progress without state tracking; this pattern provides a recoverable workflow using local state files and captured comment IDs to resume work seamlessly after interruptions.