git-workflow
/git-workflow
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.
- Author
- JetBrains ↗
- Repository
- ideavim ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author 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.
How it works
- Branching
- Commits
- Pull Requests
- Issue Tracking
SKILL.md preview
--- 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. --- # 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 fix ``` **Content 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
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · JetBrains/ideavim | 100 | MIT |
| event4u-app/agent-config | 100 | MIT |
| lee-w/maigo | 100 | MIT |
| hakula139/plugins | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| Sanit-mann/The-Insectoids | 100 | MIT |
| eliyce/paqad-ai | 100 | MIT |
| langfuse/langfuse | 100 | MIT |
| Muvon/octomind-tap | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version bff0cc9ae3f7 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100git-practices
Git conventions for branches, commits, and pull requests. Load this skill whenever creating branches, writing commit messages, or opening PRs. Trigger on any git workflow operation — commits, branches, pull requests, or merge operations. - 100changelog
Maintains the IdeaVim changelog (CHANGES.md). Use when updating the changelog, documenting releases, or reviewing commits/PRs for changelog entries. - 100managing-git
Manages Git workflows including branching, commits, and pull requests. Use when working with Git, creating commits, opening PRs, managing branches, resolving conflicts, or when asked about version control best practices. - 100git
Guide for Git operations including commits, branches, rebasing, and conflict resolution. Use when working with version control, creating commits, managing branches, or resolving merge conflicts. - 90conventions-git
Git and pull-request default conventions — trunk-based branches, conventional commits, atomic commits, history safety, PR size and description. Use when creating branches, writing commit messages, committing, or opening pull requests. - 100git
Apply Epicenter Git conventions for commits, branches, and history. Use when staging files, writing or splitting commits, creating branches, or inspecting history, not for pull request text or merge guidance.