skills.rest
theZMC
theZMCCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

work-github-issue

Automate GitHub issue workflows with gh CLI, branching, PRs, and merges.

2|Updated Aug 20, 2024
Search Tags:#automation#github#branching#code-review#pull-request#issue-management#gh-cli
One-click install
npx skills add https://github.com/theZMC/dotfiles --skill work-github-issue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-github-issue
Source: https://github.com/theZMC/dotfiles/tree/main/.agents/skills/work-github-issue
Command: npx skills add https://github.com/theZMC/dotfiles --skill work-github-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end workflow for handling GitHub issues, reducing manual steps and ensuring consistency across branch creation, commits, PRs, and merges.

Core Features & Use Cases

  • End-to-end GitHub issue workflow automation using gh CLI to read an issue, create a feature branch, implement changes, and prepare a signed commit.
  • Open a pull request, request Copilot review, triage feedback, and perform a final fast-forward merge after user approval.
  • Enforces guardrails: single signed commit, proper branch naming, and required checks before merging.

Quick Start

Invoke this skill to process a GitHub issue end-to-end using gh CLI.

Frequently Asked Questions about work-github-issue

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

FAQPage Schema
How do I automate GitHub issue workflows end-to-end from branch creation to merge?▼

Automating GitHub issue workflows end-to-end uses gh CLI to read an issue, create a feature branch, commit changes, open a PR, and merge after approval. This ensures consistent branching, signed commits, and proper review triage.

What GitHub issue automation steps does this workflow handle using gh CLI?▼

The GitHub issue automation steps include reading the issue, creating a feature branch, preparing a signed commit, opening a pull request, requesting Copilot review, triaging feedback, and performing a fast-forward merge after user approval.

Do I need a specific gh CLI version to automate Copilot review for pull requests?▼

Yes, automating Copilot review for pull requests requires gh CLI version 2.88.0 or higher with Copilot support. You also need authenticated access to the target repository and a configured git signing setup.

Can I use this GitHub issue automation with an unclean working tree?▼

No, this GitHub issue automation requires a clean working tree before processing. It enforces guardrails including a single signed commit, proper branch naming, and required checks before merging to maintain repository consistency.

What's the best way to enforce a single signed commit and proper branch naming for GitHub issues?▼

Enforcing a single signed commit and proper branch naming is handled automatically during GitHub issue workflow automation. The process applies guardrails before merging to ensure commits are signed and branches follow naming conventions.

Why does GitHub issue workflow automation require user approval before the final merge?▼

GitHub issue workflow automation requires user approval before the final merge to ensure human oversight. After Copilot triages feedback on the pull request, the automation performs a fast-forward merge only when explicitly approved.

Related Skills

Explore More Software Engineering Skills→
PlaidmustachePlaidmustache

github-auth

Configure Hermes Agent GitHub authentication via tokens, SSH keys, or gh CLI.

Community
Intermediate
lugassawanlugassawan
2

workflow-cleanup-merged

Clean up local worktrees and merged branches after a GitHub PR.

Community
Advanced
roanbrasilroanbrasil
5

static-analysis

Automate static analysis for Java, Kotlin, Python, and Rust codebases.

Community
Advanced
BenjaminRose805BenjaminRose805

git-operations

Automate Git branch, commit, and worktree workflows with CLI validation.

Community
Intermediate