skills.rest
gullitmiranda
gullitmirandaCOMMUNITY
Explore all skills by this author →
GitHub

pr

Automates pull request creation and validation using GitHub CLI.

2|Updated Oct 10, 2025
Search Tags:#automation#review#pr#quality-gates#pull-request#conventional-commits#gh-cli
One-click install
npx skills add https://github.com/gullitmiranda/.cursor --skill pr-gullitmiranda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/gullitmiranda/.cursor/tree/main/skills/pr
Command: npx skills add https://github.com/gullitmiranda/.cursor --skill pr-gullitmiranda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines end-to-end PR workflows, ensuring quality gates, conventional commits, and ready-for-review readiness.

Core Features & Use Cases

  • PR creation: Create pull requests using gh CLI with validated titles and descriptions.
  • Quality gates: Run tests, linting, and checks before PR creation.
  • Readiness management: Mark PR as ready for review with appropriate labels and reviewers.
  • Use Case: Triggered when preparing a PR touching multiple components to ensure traceability and policy compliance.

Quick Start

Create a feature branch, commit changes with a conventional message, then issue /pr to start the PR workflow.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate pull request creation and validation using GitHub CLI?▼

Automate pull request creation and validation by triggering the PR workflow, which uses GitHub CLI to enforce conventional commit formatting, description completeness, and quality gate checks before submission.

What quality gates are enforced before creating a pull request?▼

Quality gates enforced before creating a pull request include running tests, linting, and checks, while validating that the feature branch is ahead of the base branch and uses conventional commit messages.

Do I need conventional commits to automate PR readiness management?▼

Yes, conventional commits are required to automate PR readiness management, as the workflow validates commit formatting and description completeness before marking the pull request ready for review with labels and reviewers.

Can I integrate Linear when creating a pull request with gh CLI?▼

Yes, Linear integration is optionally supported during PR creation with gh CLI to ensure traceability and policy compliance when preparing a pull request touching multiple components.

What are the prerequisites for automating an end-to-end PR lifecycle?▼

Prerequisites for automating an end-to-end PR lifecycle include GitHub CLI authentication, a feature branch with conventional commits, and the branch being ahead of its base to satisfy ready check requirements.

Why is my PR workflow not marking the pull request as ready for review?▼

Your PR workflow may not mark the pull request as ready for review if quality gates fail, conventional commit formatting is invalid, or the feature branch is not ahead of the base branch.

Related Skills

Explore More Software Engineering Skills→
dtorrasdtorras

fix-github-issue

Create feature branches, implement fixes, and open PRs via gh CLI.

Community
Advanced
tizeetizee
2

requesting-code-review

Automate early code review feedback with structured severity categorization.

Community
Intermediate
stharroldstharrold

quality-enforcer

Automates Django project testing and test-result reporting.

Community
Intermediate
sobhanashinesobhanashine
1

land-and-deploy

Automate code merge, CI/CD pipeline, and production health verification workflows.

Community
Intermediate