create-pr

Create GitHub pull requests for the FluidFramework repository with branch validation and changeset checks.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/tylerbutler/repo-overlays --skill create-pr-tylerbutler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/tylerbutler/repo-overlays/tree/main/tylerbutler/FluidFramework/jikim-superskills/.claude/skills/create-pr
Command: npx skills add https://github.com/tylerbutler/repo-overlays --skill create-pr-tylerbutler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of creating GitHub pull requests, ensuring all necessary checks and information are included, reducing manual effort and potential errors.

Core Features & Use Cases

  • Automated Branch Verification: Checks if you are on a feature branch and have commits ahead of main.
  • Changeset Management: Guides you to create necessary changeset files for package updates.
  • PR Information Gathering: Prompts for essential PR details like title, description, and test plan.
  • Use Case: After completing a feature, use this Skill to push your branch and create a well-formatted pull request with all required information, ready for review.

Quick Start

Use the create-pr skill to generate a pull request for your current branch.

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?

You can automate GitHub pull request creation by using a skill that validates your branch state, checks for changeset files, and gathers PR details before pushing and executing the `gh pr create` command. This reduces manual effort and potential errors.

What is the process for creating a pull request with changeset files?

Creating a pull request with changeset files involves validating that your feature branch has commits ahead of main, verifying necessary changeset files exist for package updates, and prompting for essential details like title and description before pushing the branch.

Do I need to use the GitHub CLI to create a pull request?

Yes, this automation relies on the GitHub CLI to execute the `gh pr create` command. It pushes your prepared branch and formats the pull request with all required information, ready for review.

What's the best way to enforce branch naming and PR title conventions?

To enforce branch naming and PR title conventions, use an automated pull request creation process that validates your branch state and prompts for properly formatted titles before submitting the request to GitHub.

Why does my pull request creation fail without a changeset file?

Pull request creation fails without a changeset file because the automation checks for necessary changeset files when package updates are detected. It guides you to create them before allowing the branch to push and the PR to open.