create-pr

Automate GitHub pull request creation with lint, test, and security checks.

577|48|Updated Aug 4, 2025
One-click install
npx skills add https://github.com/FradSer/dotclaude --skill create-pr-fradser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/FradSer/dotclaude/tree/main/github/skills/create-pr
Command: npx skills add https://github.com/FradSer/dotclaude --skill create-pr-fradser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates GitHub pull request creation with integrated quality checks, reducing manual coordination and error-prone PR workflows.

Core Features & Use Cases

  • Atomic commits enforcement: Each change is committed as a single logical unit.
  • Quality gates: Lint, tests, and security checks are executed automatically before PR submission.
  • Issue linkage and labeling: Automatically link related issues and apply conventional labels for traceability.
  • Automated PR creation: Generate PRs with descriptive titles and standardized bodies that follow the project's conventions.

Quick Start

Use the create-pr skill to submit a PR for the current branch after lint and tests pass.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate GitHub pull request creation with quality checks?

Automating GitHub pull request creation with quality checks involves running lint, tests, and security validations before submission. This skill orchestrates gh and git tooling to enforce atomic commits, conventional messages, and meticulous PR bodies for repeatable results.

Can I enforce atomic commits and conventional commit messages before opening a PR?

Enforcing atomic commits and conventional commit messages before opening a PR ensures each change is a single logical unit. This skill validates code quality and orchestrates git tooling to maintain traceability and standardized PR bodies automatically.

What is the best way to link related issues and apply labels during PR automation?

Linking related issues and applying labels during PR automation requires orchestrating GitHub tooling to connect trackers and enforce conventions. This skill automatically applies consistent labels and links issues to ensure traceability before opening the pull request.

Does this PR automation run lint and tests locally before submitting to GitHub?

Running lint and tests locally before submitting to GitHub is a core quality gate of this PR automation. It executes security checks, validates code, and generates descriptive titles with standardized bodies only after all validations pass.

Why should I use automated quality gates for pull request workflows?

Automated quality gates for pull request workflows reduce manual coordination and error-prone submissions. By validating code through lint, tests, and security checks before opening a PR, you ensure traceability, atomic commits, and consistent labeling.

Do I need the gh CLI tool to automate pull request generation and validation?

Automating pull request generation and validation requires the gh CLI tool to orchestrate GitHub operations. This skill uses gh and git tooling to enforce quality checks, link issues, apply labels, and create PRs with conventional commit messages.