pr

Stage changes, commit with conventional messages, and open a GitHub PR.

11|6|Updated Nov 15, 2025
One-click install
npx skills add https://github.com/mako-ai/mako --skill pr-mako-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/mako-ai/mako/tree/main/.cursor/skills/pr
Command: npx skills add https://github.com/mako-ai/mako --skill pr-mako-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit changes and open a pull request from the current workspace, streamlining code reviews and collaboration.

Core Features & Use Cases

  • Stage changes, write conventional commit messages, push to the remote repository
  • Automatically open a PR on GitHub with a generated title and body
  • Return the PR URL to share with teammates and reviewers

Quick Start

Create a pull request for the current changes and open it on GitHub.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I open a pull request for local git changes from my workspace?

To open a pull request, stage your local git changes, compose a conventional commit message, push to a remote branch, and generate a structured GitHub PR to get a shareable URL.

What's the best way to generate a conventional commit message before pushing a PR?

Generating a conventional commit message for a PR involves staging changes and structuring the title and body to accurately describe the code modifications before pushing to the remote branch.

Do I need GitHub CLI installed to open a PR from the command line?

Yes, opening a PR from the command line requires Git tooling and the GitHub CLI or an equivalent PR creating capability to push the branch and create the pull request on the remote repository.

Can I automatically stage changes and push to a remote branch in one step?

Yes, you can stage changes and push to a remote branch by staging your workspace modifications, writing a conventional commit message, and pushing the branch to prepare for opening the pull request.

How does creating a pull request handle sensitive data in the workspace?

Creating a pull request ensures that no sensitive data is exposed when staging changes, composing the commit message, and pushing the modifications to the remote GitHub repository.

What is the output URL returned after opening a GitHub pull request?

The output returned after opening a GitHub pull request is a shareable PR URL, which provides direct access to the structured title and body for teammates and code reviewers.