skills.rest
remotion-dev
remotion-devOFFICIAL
Explore all skills by this author →
Website𝕏@remotionGitHub

make-pr

Create a pull request for affected packages using the GitHub CLI.

55.9k|4.2k|Updated Jun 23, 2020
Search Tags:#automation#git#branching#monorepo#prettier#pull-request#gh-cli
One-click install
npx skills add https://github.com/remotion-dev/remotion --skill make-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: make-pr
Source: https://github.com/remotion-dev/remotion/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/remotion-dev/remotion --skill make-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of creating pull requests for newly implemented features across affected packages in a repository. It streamlines branch creation, formatting, committing, and PR creation, ensuring consistency and faster code review cycles.

Core Features & Use Cases

  • Branch & PR automation: Detects changes, creates a feature branch, formats code with Prettier, and pushes for review.
  • Standardized commits: Enforces commit message format using package names extracted from package.json for each affected package.
  • PR creation: Opens a pull request using the GitHub CLI with a consistent title and body that reflect the changes.
  • Use Case: When implementing a feature across multiple packages in a monorepo, run this Skill to auto-create a PR for the changes with a single command.

Quick Start

Run the make-pr skill to open a PR for the current feature across affected packages.

Frequently Asked Questions about make-pr

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

FAQPage Schema
How do I automate pull request creation for feature branches in a monorepo?▼

Automating pull request creation in a monorepo involves creating or reusing a feature branch, formatting code with Prettier, and using the GitHub CLI to push and open standardized PRs across affected packages.

How do I standardize commit messages across multiple affected packages?▼

Standardizing commit messages across affected packages requires extracting the target package name from package.json and enforcing a consistent commit message format for each package before pushing to the remote repository.

Can I use the GitHub CLI to open a PR with a consistent title and body?▼

Yes, using the GitHub CLI to open a PR allows you to generate a consistent title and body automatically, ensuring standardized documentation of feature changes across affected packages.

Does this PR automation workflow handle code formatting before committing changes?▼

Yes, this PR automation workflow formats code with Prettier before committing changes, ensuring that all pushed feature updates adhere to the repository's defined styling standards.

What is the best way to target the most relevant package when multiple packages are affected?▼

Targeting the most relevant package when multiple packages are affected is handled by deriving the target from package.json and intelligently selecting the primary package during the automated PR creation process.

Do I need a feature branch already created to run PR automation?▼

No, you do not need a feature branch already created; the automation process detects changes and either creates a new feature branch or reuses an existing one before committing and pushing.

Related Skills

Explore More Software Engineering Skills→
jmbeachjmbeach

backlog-sync

Create and merge GitHub PRs from local backlog directory changes.

Community
Intermediate
DisentinelDisentinel
36

/approve — Push PR to Auto-Merge

Push a feature branch, create a GitHub pull request, and enable auto-merge.

Community
Advanced
WesleySmitsWesleySmits
6

enforcing-code-linting

Lint and fix changed files in JavaScript/TypeScript pull requests with ESLint, Prettier, and stylelint.

Community
Advanced
gabrielfruetgabrielfruet
3

git-workflow

Stage, commit, and push Git changes with diff review and rebase recovery.

Community
Advanced