create-pr

Create pull requests after passing pre-flight safety checks.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/stevenmunoz/turbo-ai-exercise --skill create-pr-stevenmunoz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/stevenmunoz/turbo-ai-exercise/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/stevenmunoz/turbo-ai-exercise --skill create-pr-stevenmunoz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Create pull requests with built-in safety checks to prevent common merge mistakes and unsafe changes.

Core Features & Use Cases

  • Pre-flight checks including linting, tests, and build verification before PR creation.
  • Branch safety safeguards to ensure proper review flow and avoid unintended branch changes.
  • Firebase environment validation and documentation checks as part of the PR process.

Quick Start

Create a PR from your current branch, ensuring all pre-flight checks pass before submission.

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 safety checks?

Automated pull-request creation runs pre-flight safety checks, enforcing branch safety, build verification, tests, linting, and Firebase environment validation before opening a PR to prevent unsafe merges.

What is the best way to prevent unsafe changes and common merge mistakes in a git workflow?

Pre-flight PR checks prevent common merge mistakes by validating branch safety, running build and test verification, and checking documentation before a pull request is created to ensure proper review flow.

How do I run build verification and linting before opening a pull request?

Build verification and linting execute as pre-flight checks before pull-request creation, automatically running tests and validating code to ensure changes are safe for merging across branches.

Can I validate Firebase environments and documentation as part of an automated PR workflow?

Firebase environment validation and documentation checks execute during automated PR creation, verifying configurations and docs as pre-flight safeguards to ensure safe multi-team release coordination.

Does automated pull-request creation work for coordinating multi-team releases?

Automated pull-request creation supports multi-team release coordination by enforcing branch safety and running pre-flight checks across branches to prevent unintended changes during code review.