skills.rest
JetBrains
JetBrainsOFFICIAL
Explore all skills by this author →
Website𝕏@jetbrainsGitHub

update-pr

Stage, commit, and push updates to an existing feature branch.

Updated Aug 27, 2026
Search Tags:#automation#git#commit#quality-gates#branch-management#pull-request#update-pr
One-click install
npx skills add https://github.com/JetBrains/databao-cli --skill update-pr-jetbrains
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-pr
Source: https://github.com/JetBrains/databao-cli/tree/main/.claude/skills/update-pr
Command: npx skills add https://github.com/JetBrains/databao-cli --skill update-pr-jetbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stage, commit, and push follow-up changes to an existing feature branch or PR. Use for quick iterations.

Core Features & Use Cases

  • Stage only the relevant files (never git add -A) to keep history clean.
  • Extract ticket IDs from branch names (DBA-<number>) for consistent commit messages.
  • Push updates to the existing branch and report the PR URL when available.

Quick Start

Stage the necessary changes, commit with a ticket-prefixed message derived from the branch name if present, and push to the current feature branch.

Frequently Asked Questions about update-pr

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

FAQPage Schema
How do I commit and push updates to an existing pull request branch?▼

To commit and push updates to an existing pull request branch, you can automate staging only the selected files, committing with a ticket-prefixed message, and pushing to the upstream feature branch while reporting the PR URL.

What is the safest way to stage changes for a pull request iteration?▼

The safest way to stage changes for a pull request iteration is to stage only the relevant files explicitly, avoiding broad commands like git add -A to keep the branch history clean and prevent unintended files from entering the commit.

How do I extract a ticket ID from a git branch name for commit messages?▼

Extracting a ticket ID from a git branch name for commit messages involves parsing the branch name for patterns like DBA-<number>, automatically prefixing the commit message with this ID to maintain consistent tracking across iterations.

Can I run quality gates before pushing commits to a feature branch?▼

Yes, you can run quality gates before pushing commits to a feature branch. The automation enforces these guardrails during the staging and committing process to ensure code integrity before the push occurs.

Does this pull request update automation prevent pushing directly to main?▼

Yes, this pull request update automation includes built-in guardrails that explicitly prevent pushing directly to the main branch, ensuring all updates are safely routed to the correct feature branch or PR.

Related Skills

Explore More Software Engineering Skills→
Andresch2Andresch2

commit

Stage relevant changes and create Git commits and pull requests via GitHub CLI.

Community
Intermediate
mvillmowmvillmow
18

verify-pr-ready

Verify GitHub pull requests for CI checks, approvals, and merge conflicts.

Community
Basic
naj2rnaj2r

commit

Creates git commits with auto-generated messages and optional push.

Community
Intermediate
pfangueiropfangueiro
6

git-workflow

Standardize Git commits, branching, pull requests, and hooks.

Community
Basic