gh-workflow

Automate GitHub issues, branches, commits, and comments via the gh CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hashi-demo-lab/terraform-agentic-workflows-demo09 --skill gh-workflow-hashi-demo-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-workflow
Source: https://github.com/hashi-demo-lab/terraform-agentic-workflows-demo09/tree/main/.claude/skills/gh-workflow
Command: npx skills add https://github.com/hashi-demo-lab/terraform-agentic-workflows-demo09 --skill gh-workflow-hashi-demo-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralize and automate GitHub interactions by routing common tasks through the gh CLI, reducing manual REST calls and credential handling while enabling consistent, auditable actions across issues, branches, commits, and comments.

Core Features & Use Cases

  • Create and update issues via gh issue commands with standardized labels and assignees.
  • Create branches linked to specific issues using the NNN-short-name convention and auto-push.
  • Commit and push changes using conventional commit messages and automated guidance.
  • Post structured progress comments on issues and PRs to reflect status and outcomes.
  • Trigger actions from natural prompts like “file an issue”, “make a branch for this”, or “push my changes”.

Quick Start

Create a new GitHub issue titled 'Bug: S3 module deprecated ACL' with a descriptive body and label it as bug, then create and push a branch linked to that issue.

Frequently Asked Questions about gh-workflow

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

FAQPage Schema
How do I automate GitHub issue creation and labeling using the gh CLI?

Automating GitHub issue creation via the gh CLI routes tasks through standardized commands to apply labels and assignees, reducing manual REST calls while ensuring consistent, auditable issue tracking across repositories.

Can I create a branch linked to a specific GitHub issue and push it automatically?

Creating a branch linked to a specific GitHub issue is possible by using the gh CLI to auto-push branches following the NNN-short-name convention, establishing traceability between code changes and their originating issues.

Does the gh CLI workflow support GitHub Enterprise environments for repository operations?

The gh CLI workflow supports GitHub Enterprise environments for common repository operations, applying necessary environment checks and safeguards to ensure consistent actions across both GitHub.com and enterprise instances.

What is the best way to enforce conventional commit messages when pushing changes to GitHub?

Enforcing conventional commit messages is best handled by routing pushes through the gh CLI, which provides automated guidance and standardized commit formatting for clear, auditable repository history.

When do I need to post structured progress comments on GitHub issues and pull requests?

Posting structured progress comments on GitHub issues and pull requests is needed when updating stakeholders on status and outcomes, ensuring actions remain auditable and traceable throughout the workflow lifecycle.

Why use the gh CLI to manage GitHub workflows instead of manual REST API calls?

Using the gh CLI to manage GitHub workflows centralizes interactions and reduces manual REST API credential handling, enabling consistent, safeguarded actions for issues, branches, commits, and comments.