create-pr

Create a draft pull request after running lint, typecheck, and test scripts.

16|1|Updated Sep 24, 2025
One-click install
npx skills add https://github.com/Hey-Diga/dotclaude --skill create-pr-hey-diga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/Hey-Diga/dotclaude/tree/main/skills/create-pr
Command: npx skills add https://github.com/Hey-Diga/dotclaude --skill create-pr-hey-diga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates and safeguards the process of creating a pull request by verifying branch status, running lint/typecheck/tests, and assembling a clear PR description so untested or incomplete changes are not merged.

Core Features & Use Cases

  • Pre-flight branch checks: Detects uncommitted changes and prevents creating PRs from main/master or dirty working trees.
  • Automated quality verification: Runs lint, type checking, and test suites, surfaces failures, and supports iterative fixes before pushing.
  • Comprehensive PR drafting and push: Summarizes commits and diffs, extracts related issue numbers, drafts a descriptive PR body, pushes the branch, and creates a draft PR ready for review.
  • Use Cases: Finalizing feature branches for review, preparing bugfixes with local CI checks, and enforcing code quality before opening pull requests.

Quick Start

Create a draft pull request for the current branch after running lint, typecheck, and tests and reviewing the change summary.

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 linting and testing checks?▼

Automated pull request creation runs local lint, typecheck, and test scripts before pushing your branch. This workflow prevents merging untested changes by enforcing code quality verification and assembling a descriptive PR body.

What is the best way to create a draft pull request from a feature branch?▼

Creating a draft pull request from a feature branch involves detecting uncommitted changes, running quality verification scripts, and summarizing commits. The process pushes the branch and opens a draft PR ready for review.

Do I need GitHub CLI to create a verified pull request?▼

Yes, creating a verified pull request requires local git and GitHub CLI access. You also need a remote origin with an upstream main branch to generate diffs and executable npm scripts for linting, type checking, and testing.

Why does pull request creation fail from a dirty Git working tree?▼

Pull request creation fails from a dirty Git working tree to prevent merging incomplete changes. Pre-flight branch checks detect uncommitted changes and block the process to ensure only verified code is pushed.

Can I use this workflow for bugfix branches in npm-based repositories?▼

Yes, this workflow supports bugfix branches in npm-based repositories. It enforces local CI checks by running your lint, typecheck, and test suites before pushing the branch and creating a draft pull request.