github-pr-workflow

Create and manage GitHub pull request workflows from branch creation through merge.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/TitoPrausee/nexus-toti --skill github-pr-workflow-titoprausee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/TitoPrausee/nexus-toti/tree/main/data/skills/github/github-pr-workflow
Command: npx skills add https://github.com/TitoPrausee/nexus-toti --skill github-pr-workflow-titoprausee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the manual overhead of handling the full GitHub pull request lifecycle, helping teams create branches, open PRs, track checks, and merge changes with less context switching.

Core Features & Use Cases

  • Branch and Commit Workflow: Create feature or fix branches, stage changes, and write conventional commit messages that keep history clean and reviewable.
  • PR Creation and CI Monitoring: Open pull requests with GitHub CLI or REST API fallbacks, then monitor checks and workflow runs until the branch is ready to merge.
  • Failure Triage and Recovery: Inspect failing CI logs, identify common test, lint, type, build, permission, or timeout issues, and apply targeted fixes before retrying.
  • Merge and Cleanup: Merge via squash or auto-merge, delete the remote branch, and return the repository to a clean main branch state.

Quick Start

Ask me to create a feature branch, open a pull request, watch its CI status, and merge it when the checks pass.

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 a GitHub pull request workflow from branch creation to merge?

Automating a GitHub pull request workflow involves creating branches, enforcing conventional commits, opening PRs via GitHub CLI or API, polling CI status, and merging after checks pass. This Skill orchestrates that full lifecycle automatically.

What's the best way to monitor CI checks and triage failures before merging a pull request?

The best way to monitor CI checks is to poll workflow runs and inspect failing logs for test, lint, type, build, permission, or timeout errors. This enables targeted failure triage and recovery before attempting a pull request merge.

Do I need the GitHub CLI installed to create and manage pull requests, or can I use git and curl?

You do not need the GitHub CLI strictly installed. This Skill detects GitHub authentication and supports pull request creation, CI status polling, and merge operations using git plus curl REST API fallbacks.

Can I use conventional commits to keep git history clean when opening a GitHub pull request?

Yes, you can use conventional commits to keep git history clean when opening a GitHub pull request. This Skill stages changes and generates conventional commit messages to ensure branch history remains structured and reviewable before PR creation.

How do I handle GitHub authentication detection and remote repository parsing for automated PRs?

Handling GitHub authentication detection and remote repository parsing for automated PRs involves identifying configured credentials and extracting remote URLs. This allows the workflow to authenticate API requests and target the correct repository automatically.

Why is my pull request merge failing after CI checks pass, and how do I clean up the remote branch?

A pull request merge might fail after CI passes due to permission issues or pending reviews. This Skill manages merge operations via squash or auto-merge, deletes the remote branch, and returns the repository to a clean main branch state.