skills.rest
TeamSloppy
TeamSloppyOFFICIAL
Explore all skills by this author →
WebsiteGitHub

github-pr-workflow

Automate GitHub PR workflows with branches, commits, and merges via gh and the GitHub API.

26|1|Updated Feb 25, 2026
Search Tags:#automation#git#github#ci-cd#workflows#pull-request
One-click install
npx skills add https://github.com/TeamSloppy/Sloppy --skill github-pr-workflow-teamsloppy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/TeamSloppy/Sloppy/tree/main/Sources/sloppy/Resources/Skills/github-pr-workflow
Command: npx skills add https://github.com/TeamSloppy/Sloppy --skill github-pr-workflow-teamsloppy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub PR lifecycle automation that guides teams through branch creation, PR opening, CI checks, and merges without manual toggling or context switching.

Core Features & Use Cases

  • Branch creation and naming conventions aligned with project standards.
  • PR creation via the GitHub CLI (gh) or REST API, with documented bodies.
  • CI status monitoring and status aggregation across workflows and checks.
  • Auto-fix and re-run workflows to recover from transient CI failures and promote faster merges.

Quick Start

Create a feature branch, push it to origin, and open a PR using gh pr or the GitHub API.

Frequently Asked Questions about github-pr-workflow

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

FAQPage Schema
How do I automate GitHub PR workflows from branch creation to merge?▼

Automating GitHub PR workflows involves orchestrating branch creation, PR opening via gh or the GitHub API, CI status monitoring, and automated merge pipelines. This Skill handles the entire lifecycle to eliminate manual toggling and context switching in collaborative projects.

Can I monitor CI status checks and aggregate workflows for a pull request?▼

Yes, CI status monitoring aggregates checks across workflows for a pull request. It tracks CI status and applies auto-fix or re-run workflows to recover from transient CI failures, promoting faster merges without manual intervention.

What is the best way to handle transient CI failures in GitHub pull requests?▼

Handling transient CI failures in GitHub pull requests is managed through auto-fix and re-run workflows. The automation detects transient failures and re-runs the workflows automatically to recover, ensuring consistent PR handling and promoting faster merges.

Do I need the GitHub CLI or REST API to orchestrate pull request merges?▼

You can use either the GitHub CLI (gh) or the REST API to orchestrate pull request merges. The automation supports both methods for PR creation, status checks, and merge orchestration, requiring environment-aware tokens for authentication.

How does environment-aware token usage work for GitHub API automation?▼

Environment-aware token usage for GitHub API automation ensures appropriate authentication tokens are applied based on the environment. This satisfies security requirements for PR creation, CI monitoring, and merge orchestration without exposing credentials.

When do I need automated merge pipelines for collaborative software projects?▼

Automated merge pipelines for collaborative software projects are needed when teams require consistent PR handling. They guide branches through CI checks and merges, applying naming conventions and recovering from failures to maintain project standards.

Related Skills

Explore More Software Engineering Skills→
jporrejporre
6

b9-close

Close GitHub pull requests and resolve linked issues and worktrees.

Community
Advanced
mr-daedaliummr-daedalium
107

land-and-deploy

Merge PRs, trigger deployment, and verify canary health in CI/CD pipelines.

Community
Advanced
kys0213kys0213

git

Automate Git branch creation, TODO-based commits, and PR generation.

Community
Intermediate
afel6afel6

github-pr-workflow

Automate GitHub PR lifecycles from branch creation through merging.

Community
Advanced