pr-workflow

Automate pull request workflows with git and the GitHub CLI.

1.1k|99|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/Chorus-AIDLC/Chorus --skill pr-workflow-chorus-aidlc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-workflow
Source: https://github.com/Chorus-AIDLC/Chorus/tree/main/.claude/skills/pr-workflow
Command: npx skills add https://github.com/Chorus-AIDLC/Chorus --skill pr-workflow-chorus-aidlc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes the manual, error-prone process of turning local code changes into a clean merged pull request, reducing accidental file inclusion, failing CI, and improper merge practices.

Core Features & Use Cases

  • Branch creation & naming: Guidance for creating feature, fix, and chore branches following team conventions.
  • Staged-only commits: Best practices to stage only intended files and craft clear, multi-line commit messages.
  • PR creation & CI handling: Instructions to open PRs with the GitHub CLI, monitor CI checks, inspect failed logs, iterate fixes, and merge with squash semantics.
  • Use Case: A developer finishing a feature can follow this workflow to create a focused branch, open a descriptive PR, resolve CI failures, and merge without leaving temp files or broken tests.

Quick Start

Create a branch from your current HEAD, stage only the intended files, push to origin, open a pull request with the GitHub CLI, monitor CI results, fix any failures, and squash-merge when green.

Frequently Asked Questions about pr-workflow

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

FAQPage Schema
How do I automate the pull request workflow from local code changes to a merged PR?

You can automate the pull request workflow by creating a branch, staging only intended files, pushing to an origin remote, opening a PR with GitHub CLI, monitoring CI checks, and squash-merging when green.

What is the best way to ensure only staged files are committed to a git branch?

The best way to ensure only staged files are committed is to stage specific intended files manually, craft clear multi-line commit messages, and follow branch naming conventions before pushing to the origin remote.

How do I check CI run logs and fix failures for a GitHub pull request?

To check CI run logs and fix failures, use the GitHub CLI to inspect failed CI logs, iterate fixes locally, push the updates, and monitor the CI checks until they pass before merging.

Does this PR workflow require the GitHub CLI and an origin remote?

Yes, this PR workflow requires a git repository using an origin remote and the GitHub CLI to create branches, open pull requests, inspect CI runs, and perform squash-merges with branch deletion.

Why should I use squash-merge with branch deletion when merging a pull request?

Squash-merge with branch deletion standardizes the merge process by condensing commits into a single clean commit and removing the temporary branch, reducing accidental file inclusion and improper merge practices.

How do I create feature and fix branches following team naming conventions for a pull request?

Create feature, fix, and chore branches from your current HEAD following team naming conventions, stage intended files, push to origin, and open a descriptive pull request with the GitHub CLI.