create-pr

Stage, commit, and open a GitHub PR from the current branch.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JetBrains/databao-cli --skill create-pr-jetbrains
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/JetBrains/databao-cli/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/JetBrains/databao-cli --skill create-pr-jetbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end PR creation by staging, committing, and opening a GitHub PR from the current branch.

Core Features & Use Cases

  • Stage specific changes and commit with proper prefixes, without risking main or bulk operations.
  • Pause for user confirmation before pushing and PR creation, when autosteer is not in effect.
  • Create a PR using a standardized template and report the PR URL for tracking.
  • Use case: A software engineer on a feature branch can reliably push a PR with a clean history and clear description.

Quick Start

Ask the skill to create a PR from your current branch and follow the prompts.

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 PR creation from a feature branch?

Automating GitHub PR creation involves staging specific changes, committing with proper prefixes, and pushing from your current branch. This skill validates the branch context and formats the PR description using a standardized template before reporting the resulting PR URL.

How does branch validation prevent pushing commits to main?

Branch validation enforces guardrails that prevent pushing commits directly to main. It checks the current branch context, blocks bulk operations, and requires explicit user confirmation before executing critical steps like pushing with the -u flag or opening a PR.

Can I extract ticket IDs and include them in my PR description automatically?

Yes, you can extract ticket IDs automatically when they are present in your branch context. The skill parses these identifiers and integrates them into a standardized PR template, ensuring clear tracking and description formatting for the resulting GitHub PR.

Do I need to manually confirm before pushing a git commit to a remote branch?

Yes, you need to manually confirm before pushing a git commit when autosteer is not in effect. The skill pauses for user approval before critical steps, ensuring you review staged changes and commit prefixes before pushing with the -u flag.

What is the best way to stage specific changes without risking bulk operations?

The best way to stage specific changes safely is by using automated guardrails that restrict bulk operations. This skill stages targeted file modifications, validates the branch context, and applies proper commit prefixes while pausing for confirmation before pushing.