skills.rest
kunallimaye
kunallimayeCOMMUNITY
Explore all skills by this author →
GitHub

git-pr-workflow

Guide pull request creation and review with titles, templates, and checklists.

Updated Feb 19, 2026
Search Tags:#git#workflow#code review#best practices#pull request#github
One-click install
npx skills add https://github.com/kunallimaye/lib-agents --skill git-pr-workflow-kunallimaye
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-pr-workflow
Source: https://github.com/kunallimaye/lib-agents/tree/main/skills/git-pr-workflow
Command: npx skills add https://github.com/kunallimaye/lib-agents --skill git-pr-workflow-kunallimaye

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the common challenges of creating inconsistent or incomplete pull requests and conducting superficial code reviews, leading to wasted time and potential bugs.

Core Features & Use Cases

  • Guided PR Creation: Ensures PRs have clear titles, detailed descriptions, and relevant metadata.
  • Comprehensive Review Checklist: Provides a structured checklist to ensure thorough code reviews covering quality, correctness, security, performance, testing, and documentation.
  • Informed Merge Strategy: Offers guidance on choosing the best merge strategy (squash, merge commit, rebase) based on project needs.
  • Use Case: A developer is about to create a PR for a new feature. They consult this Skill to ensure their PR title and description follow best practices and to understand which merge strategy is most appropriate for their team's workflow.

Quick Start

Follow the guidelines in this skill to create a pull request with a clear title and description.

Frequently Asked Questions about git-pr-workflow

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

FAQPage Schema
What is the best way to write a pull request description on GitHub?▼

A good pull request description uses a structured template to provide clear titles, relevant metadata, and comprehensive context. This ensures consistent code quality and efficient integration workflows.

How do I conduct a thorough code review for a pull request?▼

To conduct a thorough code review, use a comprehensive checklist covering code quality, correctness, security, performance, testing, and documentation. This prevents superficial reviews and potential bugs.

When should I use squash, merge commit, or rebase strategies in Git?▼

You should choose a merge strategy based on your project needs, using guidance to decide between squash, merge commit, or rebase. This informed approach maintains a clean and efficient integration workflow.

Does following a pull request workflow improve GitHub code reviews?▼

Following a pull request workflow improves GitHub code reviews by providing conventions for PR titles and structured checklists. This addresses inconsistent PRs and superficial reviews, reducing wasted time and bugs.

What should be included in a Git pull request checklist for best practices?▼

A Git pull request checklist for best practices should include reviews of code quality, correctness, security, performance, testing, and documentation. This ensures thorough reviews and consistent integration.

Related Skills

Explore More Software Engineering Skills→
YH-05YH-05
1

worktree-done

Clean up Git worktrees and branches after a merged Pull Request.

Community
Advanced
yocxy2yocxy2

land-and-deploy

Merge pull requests and verify production deployment health with canary checks.

Community
Advanced
GitnappGitnapp

requesting-code-review

Verify code changes before committing with security, regression, and quality checks.

Community
Advanced
chf3198chf3198

github-review-merge-admin

Validate GitHub pull request approvals, status checks, and merge readiness.

Community
Intermediate