skills.rest
tgautier
tgautierCOMMUNITY
Explore all skills by this author →
Website𝕏@_tgautierGitHub

github

Automate GitHub PR lifecycles with MCP Server and gh CLI.

2|1|Updated Jun 30, 2019
Search Tags:#automation#github#merge#pr#pull-request#checks
One-click install
npx skills add https://github.com/tgautier/dotfiles --skill github-tgautier
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/tgautier/dotfiles/tree/main/claude/skills/github
Command: npx skills add https://github.com/tgautier/dotfiles --skill github-tgautier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the GitHub PR workflow by providing a consistent lifecycle from creation through checks, formatting, linking issues, and post-merge cleanup, reducing manual coordination and errors.

Core Features & Use Cases

  • PR creation and formatting guidance with required fields like summary, test plan, and linked issues.
  • Merge gate checks and post-merge cleanup to ensure policy compliance and clean history.
  • Use case: when multiple teams collaborate on a feature branch, this skill automatically ensures every change is linked to an issue, a PR is prepared with the correct metadata, and the merge is gated by checks before closing.

Quick Start

Invoke the GitHub PR lifecycle workflow to manage PR creation, formatting, and merging using MCP Server when available.

Frequently Asked Questions about github

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

FAQPage Schema
How do I automate GitHub pull request lifecycles from creation to merge?▼

Automate GitHub pull request lifecycles by applying standardized steps for PR creation, formatting, issue linkage, merge gating, and post-merge cleanup using GitHub MCP Server tools with gh CLI fallback.

How do I link missing issues before merging a pull request?▼

Link missing issues before merging by fetching existing PRs, checking for linked issues, and automatically creating new issues if required metadata is absent to ensure proper PR tracking.

What's the best way to enforce merge gates and checks across multiple teams?▼

Enforce merge gates across teams by standardizing the PR lifecycle with required checks, formatting validation, and policy compliance steps before performing any branch merges.

Does this PR workflow require the GitHub MCP Server to function?▼

The PR workflow does not strictly require the GitHub MCP Server because it uses gh CLI as a fallback mechanism to execute pull request operations when the MCP Server is unavailable.

Can I standardize pull request formatting with required fields like test plans?▼

Standardize pull request formatting by enforcing required fields such as summary descriptions, test plans, and linked issues during the PR creation step of the lifecycle.

What happens to a branch after a gated merge is completed?▼

After a gated merge is completed, the workflow performs post-merge cleanup to maintain a clean repository history and ensure all policy compliance steps are finalized.

Related Skills

Explore More Software Engineering Skills→
drpedapatidrpedapati
88

github

Control GitHub issues, PRs, and runs via the gh CLI.

Community
Intermediate
phuetzphuetz
30

merge-pr

Squash-merge GitHub PRs via gh pr merge and verify MERGED state.

Community
Advanced
Chai-UnChai-Un

verify

Run formatting, linting, type checks, and tests before commits.

Community
Intermediate
hanibalskhanibalsk
2

gh-pr-handling

Automate GitHub PR creation, review, merge, and CI checks via gh CLI.

Community
Advanced