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

git-workflow

Enforce IdeaVim git workflow conventions for commits, branches, PRs, and CI.

10.2k|811|Updated Mar 9, 2011
Search Tags:#git#workflow#commits#branches#ci#pull-requests
One-click install
npx skills add https://github.com/JetBrains/ideavim --skill git-workflow-jetbrains
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/JetBrains/ideavim/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/JetBrains/ideavim --skill git-workflow-jetbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

IdeaVim git workflow conventions covering commits, branches, PRs, and CI. Use when creating commits, managing branches, creating pull requests, or reviewing git history within the IdeaVim project.

Core Features & Use Cases

  • Standard commit format: include the YouTrack ticket ID (eg VIM-XXXX) and a concise description.
  • Branching and PR workflow: create feature branches named VIM-XXXX/short-description and rebase to master to keep history linear.
  • CI and governance: ensure PRs are opened against master and pass CI checks before merging; track changes using YouTrack and update changelogs as required.
  • Change review and history: guiding code reviews and maintaining a clean, auditable git history.

Quick Start

Follow the git-workflow conventions when making a new change in IdeaVim: start with a YouTrack ticket in the commit message, create a feature branch named VIM-XXXX/short-description off master, and open a PR targeting master after tests pass.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
What commit message format is required for the IdeaVim project?▼

IdeaVim commit messages require a YouTrack ticket ID, such as VIM-XXXX, paired with a concise description to ensure traceable git history and standardized change governance.

How do I create a feature branch for an IdeaVim pull request?▼

Create a feature branch named VIM-XXXX/short-description branching off master, then rebase to master before opening a pull request to maintain a clean, linear git history.

What is the standard pull request workflow for IdeaVim changes?▼

The IdeaVim pull request workflow targets the master branch, requires passing CI checks, and involves tracking changes via YouTrack and updating changelogs before merging.

Can I use merge commits instead of rebasing for IdeaVim git history?▼

IdeaVim git workflow conventions require rebasing feature branches to master to keep history linear, avoiding merge commits to ensure a clean and auditable project history.

Do I need a YouTrack ticket before making an IdeaVim commit?▼

Yes, the IdeaVim git workflow requires a YouTrack ticket ID in the standard commit format and branch naming conventions to track changes and govern the code review process.

Related Skills

Explore More Software Engineering Skills→
shysssthanhtrishysssthanhtri

conventional-commit

Generate Conventional Commit messages from staged Git diffs with Jira ticket IDs.

Community
Intermediate
GitnappGitnapp

github-pr-workflow

Automate GitHub pull request lifecycle from branch creation to merge.

Community
Advanced
ktorioktorio
14.5k

fix-bug

Automate Ktor bug fixes from GitHub and YouTrack issues to pull requests.

Official
Advanced
MayaDispelerMayaDispeler
3

git-workflow

Enforce git commit message formats, branch naming, and pull request guidelines.

Community
Advanced