pr-workflow_skill

Overview

This skill automates creating, updating, and managing pull requests using the GitHub CLI (gh). It enforces branch protection habits, auto-assignment, and conventional commit formats to keep PRs consistent and review-ready. It complements CI checks and CodeRabbit review integration for reliable merge workflows.

How this skill works

The skill provides CLI patterns and small wrappers that create draft PRs, extract PR numbers, and auto-assign the creator using gh API calls. It prescribes branch naming, commit message templates, and echo wrappers to prevent terminal buffering. It also outlines checks for CI status and CodeRabbit review handling so PRs are only marked ready when requirements are met.

When to use it

• Creating or updating a single pull request from a feature/fix/chore branch
• Setting up or enforcing branch protection and naming conventions
• Formatting commits and PR titles to meet conventional commit and Jira-key requirements
• Monitoring CI checks and responding to automated CodeRabbit feedback
• Auto-assigning PRs to the current user to standardize ownership

Best practices

• Never work directly on main; always create a feature/fix/chore branch
• Auto-assign PRs to the current user using gh api user --jq '.login'
• Use echo wrappers around gh commands to avoid terminal buffering issues
• Include the Jira key in branch names, commits, and PR titles
• Always pass --repo owner/repo to gh commands to avoid wrong-repo context

Example use cases

• Create a draft PR, auto-assign it, and keep it in draft until CI passes and CodeRabbit feedback is addressed
• Apply branch protection rules and naming conventions across feature branches to simplify reviews
• Use the echo wrapper pattern when scripting gh commands in CI or local automations
• Follow conventional commit templates so changelogs and release notes are consistent
• Use GraphQL/gh for threaded review replies and to programmatically mark PRs ready after checks pass