create-pr

Create standardized pull requests with pre-flight validation and test execution.

5|1|Updated Oct 18, 2019
One-click install
npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill create-pr-marshall-hallenbeck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/Marshall-Hallenbeck/dot_files/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill create-pr-marshall-hallenbeck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh.

What problem does it solve?

This Skill eliminates the inconsistency and manual overhead of creating pull requests by enforcing pre-flight checks, test validation, and structured documentation.

Core Features & Use Cases

  • Automated Validation: Automatically verifies that tests pass and the branch is not main before proceeding.
  • Context Gathering: Aggregates git logs and diff statistics to provide a comprehensive overview of changes.
  • Use Case: Use this when you have finished a feature and want to ensure your PR is perfectly formatted, tested, and ready for review without manually typing out the summary or checking branch status.

Quick Start

Run the create-pr skill with a descriptive title to initiate the automated validation and pull request creation process.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate pull request creation with pre-flight checks?

Automating pull request creation involves running pre-flight branch validation, executing test suites, and analyzing git diffs to push changes and open standardized pull requests. This enforces quality control before merging.

Do I need the GitHub CLI to automate pull request workflows?

Yes, automating pull request workflows requires the GitHub CLI (gh) and a local git environment. These dependencies are necessary to push local changes and open pull requests directly from your branch.

How does automated git diff analysis improve pull request documentation?

Automating pull requests aggregates git logs and diff statistics to generate structured documentation. This provides a comprehensive overview of changes, ensuring consistent formatting and context for code review.

Can I use automated pull request validation on the main branch?

No, automated pull request validation verifies that your current branch is not main before proceeding. This prevents accidental direct commits to the main branch and ensures proper workflow branching.

What is the best way to standardize pull request formatting?

Standardizing pull request formatting is best achieved by automating test validation and aggregating git diff statistics. This eliminates manual overhead and enforces consistent documentation across software development workflows.