PR Workflow

The PR Workflow skill is a specialized tool for developers and engineering teams using Claude Code to manage the pull request lifecycle efficiently. It eliminates the manual effort involved in documenting code changes by leveraging git commit history, linked issues, and project-specific templates. By analyzing commits and issue references, it creates comprehensive, structured PR bodies that follow industry best practices, such as grouping changes by conventional commit types like feat, fix, chore, docs, and refactor. This skill is intended for software engineers aiming to maintain high-quality documentation standards with minimal overhead, ensuring that reviewers have all the necessary context to assess changes effectively.

• Automatically generates PR descriptions by parsing commit logs and extracting issue numbers from branch names.

• Provides context-aware templates tailored to the specific work type, ensuring consistent summary, testing checklist, and root cause sections.

• Integrates directly with the GitHub CLI (gh) to streamline the creation, editing, and lifecycle management of pull requests.

• Supports automated reviewer assignment by parsing .github/CODEOWNERS files based on modified file paths.

• Enables complex workflow automation, such as setting PR labels, assigning milestones, and configuring auto-merge strategies when CI checks pass.

• Facilitates efficient status monitoring, including draft conversion, readiness toggling, and CI/CD orchestration.

• Use this skill when initiating a new PR, updating metadata for existing ones, or managing multiple pending reviews.

• Ensure commit messages adhere to conventional commit standards to maximize the quality of the auto-generated descriptions.

• Inputs typically include the current git branch context, commit ranges, and repository issue metadata; outputs are fully formed PR bodies and shell-based executions of gh commands.

• Constraints include a dependency on a properly configured GitHub CLI environment and the existence of a corresponding remote tracking branch.

• Best practices include linking issues using the Closes #N syntax to ensure seamless project tracking and using descriptive commit messages for better automated summaries.