PR Lifecycle Management

Comprehensive workflows for managing pull requests using GitHub CLI (gh ), including CI checks, CodeRabbit reviews, stacked PRs, and branch protection.

Core Principles

• Never Work on Main - All work must happen on feature/fix/chore branches

• Auto-Assignment - Always assign PRs to the current user after creation

• Prevent Terminal Buffering - Use echo wrappers for gh commands

• Conventional Commits - Follow conventional commit format for all commits

Skill Contents

Sections

• Core Principles

• Workflow Overview

• Quick Reference

• Stacked PRs

• CodeRabbit Integration

• References

• Skill Dependencies

Available Resources

references/ - Detailed documentation

• branch protection

• coderabbit integration

• commit formats

• pr creation

• troubleshooting

Workflow Overview

Phase Description Reference

Branch Setup Create feature branches, never commit to main references/branch-protection.md

PR Creation Create draft PRs with proper formatting references/pr-creation.md

CI & Reviews Monitor CI, respond to CodeRabbit references/coderabbit-integration.md

Commits Use conventional commit format references/commit-formats.md

Quick Reference

Branch Naming Convention

{type}/{JIRA-KEY}-{description}

• feat/

• New features

• fix/

• Bug fixes

• chore/

• Maintenance

• docs/

• Documentation

• refactor/

• Code restructuring

Prevent Terminal Buffering

Always use echo wrapper for gh commands

echo "Checking..." ; gh pr checks 123 --repo owner/repo ; echo "Done"

Create and Assign PR

CURRENT_USER=$(gh api user --jq '.login')

PR_URL=$(gh pr create --draft
--title "[JIRA-KEY] fix(security): description"
--body "## Summary..."
--repo owner/repo 2>&1)

PR_NUMBER=$(echo "$PR_URL" | grep -oE '[0-9]+$') gh pr edit $PR_NUMBER --repo owner/repo --add-assignee "$CURRENT_USER"

Stacked PRs

For dependent changes, use stacked PRs with proper visualization:

PR Title Format

[JIRA-KEY] type(scope): description (PR N/M)

Stack Visualization (in PR Description)

PR Stack

Merge Flow (Not Rebase)

After fixing issues in PR #79

git checkout feat/pr-80-branch git merge feat/pr-79-branch --no-edit git push origin feat/pr-80-branch

Repeat for subsequent PRs in stack

See .claude/skills/stacked-prs for complete stacked PR workflows.

CodeRabbit Integration

Key Requirements

• All CI checks must pass before marking ready

• Address all CodeRabbit comments including nitpicks

• CodeRabbit approves automatically after addressing feedback

Co-Author for CodeRabbit Fixes

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

See .claude/skills/coderabbit-workflow for detailed patterns.

References

Reference Content

references/branch-protection.md

Branch naming, never commit to main

references/pr-creation.md

PR creation with auto-assignment

references/coderabbit-integration.md

CodeRabbit status checks and thread replies

references/commit-formats.md

Commit message templates with attribution

references/troubleshooting.md

Common issues and solutions

Best Practices

• Auto-assign PRs to current user using gh api user --jq '.login'

• Include Jira key in branch names, commits, and PR titles

• Always use echo wrapper for gh commands to prevent buffering

• Always specify --repo owner/repo to avoid directory context issues

• Use GraphQL API for review threads, comments, and replies

• Work on other tasks while CI runs - Don't block on CodeRabbit reviews

Skill Dependencies

Skill Purpose

coderabbit-workflow

Thread replies, comment export, local CLI reviews

jira-workflow

Ticket creation and Jira key integration

stacked-prs

Stacked PR management and merge workflows

Related

• .claude/skills/coderabbit-workflow

• Detailed CodeRabbit workflow patterns

• .claude/skills/jira-workflow

• Jira ticket workflow

• .claude/skills/stacked-prs

• Stacked PR management