make-pr

Automates formatting, committing, pushing, and opening PRs via gh CLI and bunx oxfmt.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Animesh-Kr/claude-skills --skill make-pr-animesh-kr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-pr
Source: https://github.com/Animesh-Kr/claude-skills/tree/main/remotion-main/.claude/skills/pr
Command: npx skills add https://github.com/Animesh-Kr/claude-skills --skill make-pr-animesh-kr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the workflow to open a PR for the current feature by standardizing formatting, committing, pushing, and PR creation, reducing manual steps and friction.

Core Features & Use Cases

  • Automatically format changed packages with bunx oxfmt --write.
  • Commit changes using the standardized "[package-name]: [commit-message]" format.
  • Push to a feature branch and create a PR via the gh CLI with a consistent title.

Quick Start

Switch to a feature branch and run the PR flow to automatically format, commit, push, and open a pull request.

Frequently Asked Questions about make-pr

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

FAQPage Schema
How do I automate creating a pull request and pushing a feature branch?

You can automate the pull request workflow by running a single command that formats code, commits changes, pushes to a feature branch, and opens a PR using the gh CLI.

How do I format code and commit changes before opening a GitHub PR?

Code is automatically formatted using bunx oxfmt --write before changes are committed with a standardized message, pushed to a branch, and submitted as a pull request.

Can I open pull requests in multi-package repositories without manually selecting the package?

Yes, the PR workflow applies to multi-package repositories and automatically selects the most relevant package for the pull request when multiple packages are affected.

What is the standardized commit message format for automated PR creation?

The standardized commit message format follows the pattern "[package-name]: [commit-message]" to ensure consistency across automated commits and pull requests.

Does automated PR creation work with the gh CLI and feature branches?

Yes, the automated workflow pushes your changes to a feature branch and creates the pull request directly via the gh CLI, standardizing the entire submission process.

What is the best way to streamline code review and branch management for feature development?

The best way to streamline code review and branch management is to standardize formatting, committing, pushing, and PR creation into a single automated workflow command.