pr-create

Name: pr-create
Availability: InStock
Author: nikhilsitaram

Create a review-ready GitHub pull request from completed code changes.

89|7|Updated Feb 25, 2026

Search Tags:#git #testing #code review #pull request #github #branch management #rebase

Ready to run

npx skills add https://github.com/nikhilsitaram/claude-caliper --skill pr-create-nikhilsitaram

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-create
Source: https://github.com/nikhilsitaram/claude-caliper/tree/main/skills/pr-create
Command: npx skills add https://github.com/nikhilsitaram/claude-caliper --skill pr-create-nikhilsitaram

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a finished code change into a safe, review-ready pull request without skipping tests, branch hygiene, or documentation updates.

Core Features & Use Cases

Branch safety: Avoids direct commits to the default branch and creates a feature branch when needed.
Validation before sharing: Reviews docs, runs tests, stages only the intended files, and rebases onto the correct target branch.
PR creation: Pushes the branch and opens a GitHub pull request with a clear summary.
Use case: When a feature is complete and the team needs it reviewed, this Skill packages the work into a clean PR for external feedback.

Quick Start

Use pr-create to commit your finished changes, push the branch, and open a pull request for review.

Frequently Asked Questions about pr-create

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

FAQPage Schema

How do I create a review-ready pull request from completed code changes?▼

To create a review-ready pull request, the Skill stages intended files, runs tests, rebases onto the correct target branch, pushes with controlled git behavior, and executes gh pr create with a structured summary body for review.

What's the best way to prevent direct commits to the default branch when opening a GitHub PR?▼

To prevent direct commits to the default branch, branch safety mechanisms detect the base branch and automatically create a feature branch before staging files, ensuring your pull request targets the correct branch.

Do I need conventional commit formatting to use this pull request workflow?▼

Yes, conventional commit formatting is required for this pull request workflow. The Skill enforces commit message standards before validating documentation, running tests, and pushing the branch to GitHub.

How does rebasing work before pushing a feature branch for code review?▼

Rebasing before pushing a feature branch updates your commits onto the correct target base branch. The Skill detects the proper base, applies the rebase, and performs a controlled git push to prepare for PR creation.

Can I run tests and documentation checks before opening a GitHub pull request?▼

Yes, you can run tests and documentation checks before opening a GitHub pull request. The Skill executes validation steps including test runs and doc reviews before pushing the branch and creating the PR.

Why does my git push fail when trying to create a pull request after rebasing?▼

Git push may fail after rebasing due to controlled push behavior restrictions. The Skill enforces branch safety and correct base-branch detection, requiring proper rebase completion and conventional commit formatting before pushing.