
Git Workflow
- 4 installs
- 10.2k repo stars
- Updated August 4, 2026
- jetbrains/ideavim
git-workflow skill documents IdeaVim git workflow conventions covering commits, branches, PRs, and CI.
About
git-workflow skill documents IdeaVim git workflow conventions covering commits, branches, PRs, and CI. Use when creating commits, managing branches, creating pull requests, reviewing git history, or any git-related activity in the IdeaVim project.. name: git-workflow description: IdeaVim git workflow conventions covering commits, branches, PRs, and CI. Use when creating commits, managing branches, creating pull requests, reviewing git history, or any git-related activity in the IdeaVim project.
- IdeaVim git workflow conventions covering commits, branches, PRs, and CI.
- Platform-specific setup patterns for git-workflow.
- Evidence-backed steps from upstream SKILL.md.
- When-to-use criteria for git-workflow versus alternatives.
Git Workflow by the numbers
- 4 all-time installs (skills.sh)
- Ranked #580 of 782 Skill Development skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
git-workflow capabilities & compatibility
- Capabilities
- git workflow quick start · git workflow when to use guidance · git workflow integration patterns
- Use cases
- documentation
- IDEs
- intellij · jetbrains
What git-workflow says it does
**Master** is the trunk and MUST always be in a "ready to release" state
Use **feature branches** for development work
npx skills add https://github.com/jetbrains/ideavim --skill git-workflowAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 4 |
|---|---|
| repo stars | ★ 10.2k |
| Last updated | August 4, 2026 |
| Repository | jetbrains/ideavim ↗ |
How do I use git-workflow correctly?
IdeaVim git workflow conventions covering commits, branches, PRs, and CI. Use when creating commits, managing branches, creating pull requests, reviewing git history, or any git-related activity in th
Who is it for?
Teams implementing git-workflow workflows from the catalog.
Skip if: Skip when requirements clearly match a different specialized stack.
When should I use this skill?
User asks about git-workflow, ideavim git workflow conventions covering commits, branches, prs, and ci. use when creatin.
What you get
Working git-workflow setup with validated configuration and next steps.
Files
Git Workflow
Branching
- Master is the trunk and MUST always be in a "ready to release" state
- Use feature branches for development work
- Naming:
VIM-XXXX/short-description(e.g.,VIM-3948/editor) - Rebase to master frequently to avoid large conflicts
- Small, isolated changes (bug fixes, minor tweaks) MAY go directly to master
- Unfinished changes MAY be committed to master only if they do NOT break functionality
- Use rebase for integration, not merge commits (linear history)
Commits
Standard format:
VIM-XXXX Description of the change- Start with the YouTrack ticket ID when the change relates to a ticket
- Example:
VIM-3948 Traverse vertical panes in ConfigurableEditor
Auto-closing format (moves YouTrack ticket to "Ready To Release"):
fix(VIM-XXXX): Description of the fixContent rules:
- Each commit MUST contain a single, focused, meaningful change
- MUST NOT include unrelated changes (formatting, unrelated refactoring)
- Include appropriate tests with behavioral changes
Pull Requests
- PRs target
master - CI runs standard tests automatically (
./gradlew test -x :tests:property-tests:test -x :tests:long-running-tests:test) - PRs from external contributors are listed in the changelog under "Merged PRs"
Issue Tracking
- Use YouTrack (not GitHub Issues) - tickets are
VIM-XXXX - URL: https://youtrack.jetbrains.com/issues/VIM
Related skills
FAQ
What does git-workflow do?
git-workflow skill documents IdeaVim git workflow conventions covering commits, branches, PRs, and CI.
When should I use git-workflow?
User asks about git-workflow, ideavim git workflow conventions covering commits, branches, prs, and ci. use when creatin.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.