skills.rest
yanochka11
yanochka11COMMUNITY
Explore all skills by this author →
GitHub

Git PR Workflow

Prepare feature branches for clean pull request reviews.

Updated May 5, 2026
Search Tags:#git#code review#pull request#github#commit hygiene#branch workflow
One-click install
npx skills add https://github.com/yanochka11/harness_bro --skill git-pr-workflow-yanochka11
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Git PR Workflow
Source: https://github.com/yanochka11/harness_bro/tree/main/.claude/skills/curated/meta/skill-factory/examples/generated/git-pr-workflow
Command: npx skills add https://github.com/yanochka11/harness_bro --skill git-pr-workflow-yanochka11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers avoid messy branches, unclear commits, and incomplete pull requests by providing a disciplined workflow for preparing changes for review.

Core Features & Use Cases

  • Branch & Commit Hygiene: Guides developers through reviewing history, cleaning commits, and preparing a focused branch.
  • CI Pre-flight Checks: Ensures tests, linters, and final validation steps are completed before opening a pull request.
  • PR Communication: Provides a structured approach for writing clear pull request titles, descriptions, and review context.

Quick Start

Use the Git PR Workflow skill to prepare my current feature branch for a clean pull request review.

Frequently Asked Questions about Git PR Workflow

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

FAQPage Schema
How do I prepare a feature branch for a clean pull request review?▼

To prepare a feature branch for a clean pull request, you need to review commit history, clean up commits, and ensure all CI pre-flight checks like tests and linters pass before opening the PR.

What is the best way to clean up Git commits before opening a pull request?▼

The best way to clean up Git commits before opening a pull request is to follow a structured branch hygiene workflow that reviews history and consolidates commits into a focused, review-ready branch.

How do I write clear pull request titles and descriptions for code review?▼

Writing clear pull request titles and descriptions for code review requires a structured communication approach that provides review context and documents the changes made in the feature branch.

Do I need to run CI checks before creating a GitHub pull request?▼

Yes, you need to run CI pre-flight checks before creating a GitHub pull request to ensure that tests, linters, and final validation steps are completed successfully.

Why does my pull request fail code review due to messy branch history?▼

Your pull request may fail code review due to messy branch history if it lacks commit hygiene and contains unclear commits that have not been cleaned up before submission.

Can I use this pull request workflow for any Git branching strategy?▼

Yes, you can use this pull request workflow for any Git branching strategy as it applies standard structured procedures for branch hygiene, testing checks, and review documentation.

Related Skills

Explore More Software Engineering Skills→
bastani-incbastani-inc
484

gh-create-pr

Commit unstaged changes, push the branch, and create a pull request.

Official
Advanced
TioSavichTioSavich

ship

Merge base branch, run tests, bump version, update changelog, commit, push, and create a pull request.

Community
Advanced
EwallywEwallyw

plankton-code-quality

Run linters and formatters on every file edit via Claude Code.

Community
Advanced
KemingHeKemingHe
9

pull-merge-request-creation

Generate GitHub and GitLab pull request descriptions from branch diffs and templates.

Community
Intermediate