skills.rest
rivkode
rivkodeCOMMUNITY
Explore all skills by this author →
Website𝕏@rivkodeGitHub

pr-guidelines

Enforce PR guidelines and templates using Conventional Commits and standardized review workflows.

Updated Apr 20, 2026
Search Tags:#git#workflow#branching#code-review#pull-request#conventional-commits#pr-guidelines
One-click install
npx skills add https://github.com/rivkode/reservation --skill pr-guidelines-rivkode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-guidelines
Source: https://github.com/rivkode/reservation/tree/main/.claude/skills/pr-guidelines
Command: npx skills add https://github.com/rivkode/reservation --skill pr-guidelines-rivkode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull Request Guidelines define a compact, consistent process for creating and reviewing PRs, ensuring changes are small, well-scoped, and easy to review.

Core Features & Use Cases

  • PR naming conventions using Conventional Commits
  • A standardized PR body template including purpose, changes, tests, checklist, review points, and screenshots
  • Central PR template file at .github/pull_request_template.md for team-wide consistency
  • Branching and merge strategy guidelines (default dev, squash/rebase/merge options)
  • Self-review and strict checklist to improve code quality before review

Quick Start

Create a draft PR following the template and ensure all checklist items are completed before requesting reviews.

Frequently Asked Questions about pr-guidelines

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

FAQPage Schema
How do I standardize pull request templates for my team's code review workflow?▼

Standardizing pull request templates involves creating a central file at .github/pull_request_template.md to enforce consistent PR bodies including purpose, changes, tests, checklists, and review points across the team. This ensures changes are small, well-scoped, and easy to review.

What should a pull request body include to streamline the code review process?▼

A pull request body should include the purpose, specific changes, tests run, a self-review checklist, review points, and screenshots. Using Conventional Commits for PR naming conventions further streamlines the review process by setting clear expectations.

Can I use Conventional Commits for pull request naming conventions?▼

Yes, you can use Conventional Commits for pull request naming conventions to codify and enforce consistent PR titles. This approach keeps changes well-scoped and aligns PR naming with standardized development workflows.

What is the best way to enforce a self-review checklist before requesting code reviews?▼

The best way to enforce a self-review checklist is to codify strict checklist items directly into the PR template. Completing these items in a draft PR before requesting reviews improves code quality and ensures changes are ready for evaluation.

Does this pull request workflow support different branching and merge strategies like squash or rebase?▼

Yes, the pull request workflow supports branching and merge strategy guidelines using a default dev branch with options for squash, rebase, or standard merges. This flexibility accommodates various team development workflows.

Related Skills

Explore More Software Engineering Skills→
sudhakrmssudhakrms
1

git-workflow

Enforce a dev-first branching model with an insiders preview channel.

Community
Intermediate
aberrantCodeaberrantCode
1

ship-to-dev

Merge feature branches into DEV after passing tests and coverage gates.

Community
Advanced
hairihouhairihou

git-conventions

Enforce Conventional Commits syntax for Git commit messages and branch naming.

Community
Basic
jefflesterjefflester
41

git-workflow

Standardize Git workflows with Conventional Commits and branch naming.

Community
Basic