new-branch-and-pr

Create a feature branch from main and open a pull request.

2.6k|204|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/cursor/plugins --skill new-branch-and-pr-cursor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-branch-and-pr
Source: https://github.com/cursor/plugins/tree/main/cursor-team-kit/skills/new-branch-and-pr
Command: npx skills add https://github.com/cursor/plugins --skill new-branch-and-pr-cursor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages end-to-end branch-to-PR workflow to ensure changes are isolated, review-ready, and traceable.

Core Features & Use Cases

  • Create a descriptive feature branch from the latest main.
  • Enforce a clean working tree and focused change scope.
  • Generate a concise PR with summary and test notes.

Quick Start

Tell the AI to start a new feature on a fresh branch from main, complete implementation and tests, then open a PR with a concise summary and test notes.

Frequently Asked Questions about new-branch-and-pr

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

FAQPage Schema
How do I automate creating a git branch and opening a pull request?

To automate creating a git branch and opening a pull request, the Skill manages the end-to-end workflow by creating a clean feature branch from main and generating a concise PR with summary and test notes.

What is the best way to ensure my feature branch is ready for code review?

The best way to ensure your feature branch is ready for code review is to enforce guardrails that verify the working tree is clean, changes are focused, and the branch targets main before opening a pull request.

How does branch automation handle uncommitted changes before opening a PR?

Branch automation handles uncommitted changes by implementing guardrails that ensure the working tree is clean before creating a new branch, preventing dirty state from polluting your pull request.

Can I generate a pull request summary automatically after finishing feature development?

Yes, you can generate a pull request summary automatically after finishing feature development. The workflow creates a PR that includes a concise summary and test notes alongside your focused changes.

Does this workflow support branching directly from the main branch?

Yes, the workflow supports branching directly from the main branch. It enforces a guardrail specifically to ensure your new descriptive feature branch targets main for proper release readiness.

When do I need an automated branch-to-PR workflow for software development?

You need an automated branch-to-PR workflow when your software development scenarios require isolated work, code review readiness, and release readiness across Git workflows to keep changes traceable.