github-operations

Automate GitHub branch naming, commits, and PR operations via MCP or gh CLI.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/cassm199-mita/azure-agentic-infraops-accelerator --skill github-operations-cassm199-mita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-operations
Source: https://github.com/cassm199-mita/azure-agentic-infraops-accelerator/tree/main/.github/skills/github-operations
Command: npx skills add https://github.com/cassm199-mita/azure-agentic-infraops-accelerator --skill github-operations-cassm199-mita

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the entire GitHub contribution lifecycle, from branch naming to PR merging, streamlining collaboration and development processes.

Core Features & Use Cases

  • Branch Naming: Enforces consistent and clear naming conventions for branches.
  • Conventional Commits: Ensures commits follow a consistent and readable format.
  • GitHub Operations: Offers MCP-first tools for GitHub issues, PRs, Actions, and releases.
  • CLI Commands: Provides a reference for using gh CLI for GitHub operations.
  • Smart PR Flow: Automates the PR lifecycle with label-based state tracking and auto-merge capabilities.

Quick Start

Create a new branch named feat/some-feature, commit changes following Conventional Commits format, and open a PR for review.

Frequently Asked Questions about github-operations

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

FAQPage Schema
How do I automate the GitHub PR lifecycle from branching to merging?

You can automate the GitHub PR lifecycle by enforcing consistent branch naming, generating conventional commits, and using smart PR flows with label-based state tracking and auto-merge capabilities.

What is the best way to standardize branch naming and conventional commits for GitHub collaboration?

Standardizing GitHub collaboration requires enforcing consistent branch naming conventions and ensuring commits follow a readable conventional format across all infrastructure and development workflows.

Can I use gh CLI commands when MCP-first tools are unavailable for GitHub operations?

Yes, GitHub operations utilize an MCP-first protocol for managing issues, PRs, Actions, and releases, with a fallback mechanism providing reference commands for using the gh CLI.

How does label-based state tracking work for GitHub pull requests?

Label-based state tracking for GitHub pull requests automates the PR lifecycle by applying specific labels to indicate review status, enabling auto-merge capabilities once criteria are met.

Do I need gh CLI installed to manage GitHub Actions and releases?

While gh CLI commands are provided as a reference fallback, the primary method manages GitHub Actions and releases using MCP-first tools, reducing strict dependency on CLI installation.