github-pr-workflow

Automate GitHub pull request lifecycle from branch creation through merge.

Updated May 14, 2026
One-click install
npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill github-pr-workflow-sethypagna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/SethyPagna/Secretary-Jarvis/tree/main/src/capabilities/skills/github/github-pr-workflow
Command: npx skills add https://github.com/SethyPagna/Secretary-Jarvis --skill github-pr-workflow-sethypagna

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of managing a GitHub pull request from start to finish, so you can branch, commit, open, monitor, and merge changes without switching between tools or guessing the next step.

Core Features & Use Cases

  • Branch and Commit Flow: Create clean feature branches and use conventional commit messages for consistent history.
  • PR Creation and Tracking: Open pull requests with either the GitHub CLI or raw API fallback, then track review and CI status.
  • CI Recovery and Merge Completion: Diagnose failed checks, apply fixes, re-run verification, and merge safely with the appropriate merge method.
  • Use Case: A developer finishes a feature, asks the Skill to prepare the branch, open the PR, watch checks, and complete the merge once the pipeline turns green.

Quick Start

Ask the Skill to help you create a feature branch, open a GitHub pull request, monitor CI, and merge it when 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 to merge?

Automating a GitHub pull request workflow involves creating a feature branch, opening a PR with conventional commit messages, tracking CI status, and merging safely once checks pass. This Skill handles the entire lifecycle from branch creation through merge and cleanup.

What's the best way to monitor CI status and diagnose failed checks on a GitHub pull request?

Monitoring CI status and diagnosing failed checks on a GitHub pull request requires tracking the pipeline results after opening the PR. This Skill automates CI recovery by diagnosing failures, applying fixes, re-running verification, and merging safely when the pipeline turns green.

Do I need the GitHub CLI to open pull requests and track code reviews?

You do not strictly need the GitHub CLI to open pull requests, as raw API fallback operations using curl are supported. This Skill requires authenticated GitHub access and a git repository with a GitHub remote, supporting gh or git plus curl-based API operations for PR creation and review tracking.

Can I use conventional commit messages and feature branches for bug fixes and feature development?

Yes, you can use conventional commit messages and feature branches for both bug fixes and feature development. This Skill applies to repository maintenance workflows, creating clean feature branches and ensuring consistent history across the entire pull request lifecycle.

Why does my pull request merge workflow fail when CI checks are still running?

A pull request merge workflow fails when CI checks are still running because safe merging requires the pipeline to turn green first. This Skill coordinates review tracking and CI monitoring to ensure checks pass before applying the appropriate merge method and completing branch cleanup.

How do I clean up git branches after merging a GitHub pull request?

Cleaning up git branches after merging a GitHub pull request is the final step in the merge workflow. This Skill automates branch cleanup following the merge completion, ensuring repository maintenance is handled end-to-end without switching between tools or guessing the next step.