Skill

github

Uses gh CLI for GitHub PR creation, squash/rebase merges, stacked PR workflows, branching strategies, and repo automation. For PR management and merging tasks.

Github

Git

Bash

devops

automation

npx claudepluginhub callstackincubator/agent-skills --plugin react-native-brownfield-migration

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Use `gh` CLI for all GitHub operations. Prefer CLI over GitHub MCP servers for lower context usage.

Supporting Assets

agents/openai.yamlreferences/stacked-pr-workflow.md

SKILL.md

Similar Skills

git-operations

Guides Git operations with conventional commits, PR workflows, squash merges, branch management, and conflict resolution. Useful for version control tasks like commits, branches, and pull requests.

3 files

all-skills

git-branch-pr-workflow

Guides Git branch management and GitHub PR workflows using main-branch development, modern git switch/restore commands, and MCP tools for creating, listing, and updating PRs.

1 file5 tools

git-plugin

github-workflow

223

Automates GitHub workflows: branching with conventional names, committing with conventional messages, pushing, pull requests, issues, and code reviews using git and gh CLI. Use for git operations like commit, push, PRs, branches, issues.

3 files

communitytools

Stats

Stars1271

Forks91

Last CommitMar 5, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

GitHub Patterns

Tools

Use gh CLI for all GitHub operations. Prefer CLI over GitHub MCP servers for lower context usage.

Quick Commands

# Create a PR from the current branch gh pr create --title "feat: add feature" --body "Description" # Squash-merge a PR gh pr merge <PR_NUMBER> --squash --title "feat: add feature (#<PR_NUMBER>)" # View PR status and checks gh pr status gh pr checks <PR_NUMBER>

Stacked PR Workflow Summary

When merging a chain of stacked PRs (each targeting the previous branch):

Merge the first PR into main via squash merge

For each subsequent PR: rebase onto main, update base to main, then squash merge

On conflicts: stop and ask the user to resolve manually

# Rebase next PR's branch onto main, excluding already-merged commits git rebase --onto origin/main <old-base-branch> <next-branch> git push --force-with-lease origin <next-branch> gh pr edit <N> --base main gh pr merge <N> --squash --title "<PR title> (#N)"

See stacked-pr-workflow.md for full step-by-step details.

Quick Reference

File

Description

stacked-pr-workflow.md

Merge stacked PRs into main as individual squash commits

Problem -> Skill Mapping

Problem

Start With

Merge stacked PRs cleanly