gh-issue

Automate GitHub issue workflows with branching, worktrees, and review gates.

6|Updated Oct 29, 2024
One-click install
npx skills add https://github.com/aram-devdocs/GoudEngine --skill gh-issue-aram-devdocs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issue
Source: https://github.com/aram-devdocs/GoudEngine/tree/main/.agents/skills/gh-issue
Command: npx skills add https://github.com/aram-devdocs/GoudEngine --skill gh-issue-aram-devdocs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the complex, multi-step process of addressing GitHub issues, ensuring a structured and traceable workflow from investigation to cleanup.

Core Features & Use Cases

  • Issue-Driven Workflow: Manages the entire lifecycle of resolving GitHub issues, including branching, implementation, review, and CI.
  • Durable Run State: Maintains a canonical run directory with plan.md and state.json for seamless resumption.
  • Strict Review Gates: Enforces sequential review processes (spec, code quality, architecture, security) and PR template adherence.
  • Automated PR Handling: Manages PR creation, monitors Claude reviews, and ensures CI green status.
  • Worktree Management: Supports isolated worktree environments for clean development.
  • Use Case: When a new bug is reported, this Skill can automatically create a dedicated branch, set up a worktree, guide the implementation, manage code reviews, and ensure the PR is merged only after all checks pass.

Quick Start

Use the gh-issue skill to start working on issue number 123.

Frequently Asked Questions about gh-issue

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

FAQPage Schema
How do I automate a GitHub issue-driven development workflow from branching to merge?

Automating GitHub issue-driven development involves orchestrating branching, isolated worktrees, sequential review gates, and PR template enforcement. A Python CLI script can manage this lifecycle by orchestrating `gh` CLI commands to ensure structured implementation and CI follow-through.

What is the best way to enforce strict code review gates on GitHub pull requests?

Enforcing strict code review gates on GitHub PRs requires sequential checks for spec, code quality, architecture, and security. Automated workflows can monitor these stages and enforce PR template adherence before allowing any merge to proceed.

How does isolated worktree management work for GitHub issue resolution?

Isolated worktree management for GitHub issues creates clean, dedicated development environments for each task. This allows developers to handle branching and implementation independently, preventing conflicts before initiating the sequential review and CI processes.

Can I resume an interrupted GitHub workflow automation if my session drops?

Yes, you can resume an interrupted GitHub workflow automation if the tool maintains a durable run state. By storing canonical `plan.md` and `state.json` artifacts in a run directory, the script can seamlessly resume the issue resolution process.

Do I need the GitHub CLI installed to automate issue lifecycle management?

Yes, you need the GitHub CLI (`gh`) installed to automate issue lifecycle management. The automation operates via a Python CLI script that directly orchestrates `gh` commands for branching, PR creation, and CI monitoring.