pr-process

Prepare commits and pull requests for this repo following the PR template and Conventional Commits.

⭐4stars🔀0forks📁View on GitHub🕐Updated Jan 4, 2026

When & Why to Use This Skill

This Claude skill automates the end-to-end Pull Request (PR) lifecycle by enforcing Conventional Commits and standardized GitHub templates. It streamlines the developer workflow by integrating commit formatting, template population, and GitHub CLI commands to ensure consistent, high-quality code contributions.

Use Cases

  • Standardizing Commit History: Automatically format commit messages according to the Conventional Commits specification to facilitate automated versioning and changelog generation.
  • Automated PR Documentation: Quickly populate complex GitHub Pull Request templates with relevant technical details, ensuring all compliance and review checklists are met before submission.
  • CLI-Driven Workflow Integration: Use the GitHub CLI (gh) to create and manage pull requests directly from the chat interface, reducing context switching between the editor and the browser.
  • Enforcing Team SOPs: Maintain repository health by strictly following squash merge protocols and standardized branch management practices as defined in the project's SOPs.
namepr-process
descriptionPrepare commits and pull requests for this repo following the PR template and Conventional Commits.

PR Process

Overview

Follow the repo PR template and semantic commit conventions. Use squash merges.

Steps

  1. Commit with Conventional Commits.
  2. Fill .github/PULL_REQUEST_TEMPLATE.md.
  3. Create PR with gh pr create --body-file.
  4. Merge with squash, no branch delete.

Resources

  • Reference: references/pr-process.md
  • Helper: scripts/pr-create.sh
  • Checklist: assets/pr-checklist.md