github-pr-workflow

Automate GitHub pull request lifecycle with branch management and CI monitoring.

Updated May 5, 2026
One-click install
npx skills add https://github.com/iani-kuli/harness_bro --skill github-pr-workflow-iani-kuli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/iani-kuli/harness_bro/tree/main/.claude/skills/ported/github-pr-workflow
Command: npx skills add https://github.com/iani-kuli/harness_bro --skill github-pr-workflow-iani-kuli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the friction of managing GitHub pull requests by providing a unified, automated workflow for branching, committing, PR creation, CI monitoring, and merging.

Core Features & Use Cases

  • Unified PR Lifecycle: Standardizes the process from branch creation to final merge using either the GitHub CLI or standard Git/curl commands.
  • Automated CI/CD Handling: Provides robust tools for monitoring CI status, diagnosing failures, and auto-fixing common issues.
  • Use Case: When a developer needs to push a feature, they can use this skill to ensure their branch follows naming conventions, create a PR with a structured body, and automatically monitor the CI pipeline until the code is ready to be squashed and merged.

Quick Start

Use the github-pr-workflow skill to create a new pull request for the current branch and monitor the CI status until completion.

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

Automating the GitHub pull request lifecycle involves standardizing branch creation, structuring PR bodies, monitoring CI/CD pipelines, and merging. This skill manages the end-to-end workflow using GitHub CLI or REST API fallback mechanisms.

Can I monitor CI/CD pipeline status and diagnose failures directly from my development environment?

Monitoring CI/CD pipeline status directly is possible via authenticated GitHub access. This skill provides tools to monitor CI status, diagnose pipeline failures, and automatically apply fixes for common CI issues.

What do I need to configure before automating pull requests with GitHub CLI and git commands?

Before automating pull requests, you need authenticated access to GitHub repositories and standard git configuration for remote operations. These prerequisites allow the skill to manage branches and interact with the CI/CD pipeline.

Does this PR automation workflow work if the GitHub CLI is not installed in my environment?

Yes, this PR automation workflow works without the GitHub CLI by falling back to standard git and curl commands using the GitHub REST API. This ensures diverse development environments can still automate PR lifecycle management.

What is the best way to standardize commit messages and branch naming conventions for GitHub pull requests?

Standardizing commit messages and branch naming conventions for GitHub pull requests is best handled by an automated lifecycle workflow. This skill enforces branching conventions and standardizes commits before creating the pull request.