skills.rest
iani-kuli
iani-kuliCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Git PR Workflow

Squash commits, rebase branches, and run local tests before pull requests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of messy, unorganized pull requests that lack context or contain unnecessary commit noise, which often leads to delayed code reviews and integration friction.

Core Features & Use Cases

  • Branch Hygiene: Provides a structured approach to squashing WIP commits and rebasing to ensure a clean, linear history.
  • CI Pre-flight: Enforces local testing and linting checks before pushing code to prevent broken builds.
  • Standardized Documentation: Guides the user in writing high-quality PR descriptions that include clear context, testing instructions, and issue linking.

Quick Start

Ask the assistant to guide you through the Git PR Workflow steps to prepare your current feature branch for a clean pull request.

Frequently Asked Questions about Git PR Workflow

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

FAQPage Schema
How do I squash WIP commits before opening a pull request?▼

Squashing WIP commits before a pull request is handled by standardizing your feature branch through git rebase operations. This ensures a clean, linear commit history and removes unnecessary commit noise for code reviews.

What's the best way to automate local testing and linting before pushing a feature branch?▼

Automating local testing and linting before pushing a feature branch is achieved through a CI pre-flight validation step. This enforces test runners like pytest or npm and linters to verify code integrity and prevent broken builds.

How does standardized documentation improve a GitHub code review process?▼

Standardized documentation improves GitHub code reviews by guiding you to write high-quality PR descriptions. These descriptions include clear context, testing instructions, and issue linking to reduce integration friction and delayed reviews.

Do I need a specific test runner to prepare my feature branch for a pull request?▼

You need local access to git, a test runner like pytest or npm, and a linter to prepare your feature branch for a pull request. These dependencies are required to validate code integrity during the CI pre-flight checks.

Can I use this workflow to rebase feature branches for a clean linear history?▼

You can use this workflow to rebase feature branches for a clean linear history. It provides a structured approach to branch hygiene by standardizing rebase operations and squashing commits before submission.

Related Skills

Explore More Software Engineering Skills→
k97k97
4

finishing-a-development-branch

Verify tests before merging or cleaning up git development branches.

Community
Intermediate
zerwizzerwiz

github-code-review

Review git diffs and pull requests for defects and quality issues.

Community
Advanced
zeronx798zeronx798

requesting-code-review

Scan staged git changes for security issues and quality regressions.

Community
Advanced
SumitRajpalSumitRajpal

squash-pr

Squash WIP commits on Git feature branches via interactive rebase.

Community
Advanced