Git GitHub Ops
c5inco/compose-pokedexer
Handles Pokedexer Git and GitHub workflows: inspect changes, prepare commit messages, manage branches and pushes, and create or update issues and pull requests with safe file-based inputs.
IdeaVim git workflow conventions covering commits, branches, PRs, and CI.
Install Git Workflow
$ npx skills add JetBrains/ideavim --skill git-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JetBrains/ideavim git-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JetBrains/ideavim.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/git-workflow .claude/skills/git-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "git-workflow" agent skill from https://github.com/JetBrains/ideavim/tree/master/.claude/skills/git-workflow into .claude/skills/git-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JetBrains/ideavim/tree/master/.claude/skills/git-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JetBrains/ideavim --skill git-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JetBrains/ideavim git-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/ideavim.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/git-workflow .agents/skills/git-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "git-workflow" agent skill from https://github.com/JetBrains/ideavim/tree/master/.claude/skills/git-workflow into .agents/skills/git-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JetBrains/ideavim --skill git-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JetBrains/ideavim git-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/ideavim.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/git-workflow .cursor/skills/git-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "git-workflow" agent skill from https://github.com/JetBrains/ideavim/tree/master/.claude/skills/git-workflow into .cursor/skills/git-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JetBrains/ideavim.git --path .claude/skills/git-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JetBrains/ideavim --skill git-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JetBrains/ideavim git-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/ideavim.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/git-workflow .gemini/skills/git-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "git-workflow" agent skill from https://github.com/JetBrains/ideavim/tree/master/.claude/skills/git-workflow into .gemini/skills/git-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JetBrains/ideavim git-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JetBrains/ideavim --skill git-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JetBrains/ideavim.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/git-workflow .github/skills/git-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "git-workflow" agent skill from https://github.com/JetBrains/ideavim/tree/master/.claude/skills/git-workflow into .github/skills/git-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JetBrains/ideavim --skill git-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JetBrains/ideavim git-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/ideavim.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/git-workflow .opencode/skills/git-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "git-workflow" agent skill from https://github.com/JetBrains/ideavim/tree/master/.claude/skills/git-workflow into .opencode/skills/git-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "git-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
git-workflow- GitHub stars
- 10k
- Token cost
- ~424 tokens
- SKILL.md length
- 167 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
IdeaVim git workflow conventions covering commits, branches, PRs, and CI.
- Creating commits
- SKILL.md covers Branching, Commits, Pull Requests and Issue Tracking
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Managing branches
What it does
Git Workflow is an agent skill from JetBrains/ideavim, published by the product's own GitHub organization. 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.
Its SKILL.md is about 420 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Git workflow and Pull requests. It works with JetBrains IDEs, Kotlin and Git. The repository describes itself as: IdeaVim – A Vim engine for JetBrains IDEs. The licence is MIT.
When your agent uses it
- Creating commits
- Managing branches
- Creating pull requests
- Reviewing git history
Example prompts
- “/git-workflow”
What it can do on your machine
Read from SKILL.md and the folder at commit 37aeff6. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
youtrack.jetbrains.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Git Workflow loads about 424 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 167 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from JetBrains/ideavim at commit 37aeff6, republished under its MIT licence (© JetBrains). 167 words, ~424 tokens.
Download SKILL.mdSave it as
.claude/skills/git-workflow/SKILL.md (or your agent's skills folder).- 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
- Naming:
- 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
© JetBrains, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/git-workflow of JetBrains/ideavim.
Open the folder on GitHubat commit 37aeff6
Compare with similar skills
Git Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Git Workflow this skillJetBrains/ideavim | 10k | — | ~424 | Automated safety check: Pass | MIT | |
| Git GitHub Opsc5inco/compose-pokedexer | 143 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Create Pull Requestcline/cline | 70k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Git Branch Namingmakeplane/plane | 61k | — | ~594 | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
Git Branch Naming
makeplane/plane
Names a new Git branch with a type prefix, the lowercased work item ID and a short kebab-case description, so the ID can be extracted later from the branch name.
- Official
Creating Description For Gh PR
redis/jedis
Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.
More from JetBrains/ideavim
- Official
Doc Sync
JetBrains/ideavim
Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.
- Official
Changelog
JetBrains/ideavim
Maintains the IdeaVim changelog (CHANGES.md). An agent skill from JetBrains/ideavim.
- Official
Extensions API Migration
JetBrains/ideavim
Migrates IdeaVim extensions from the old VimExtensionFacade API to the new @VimPlugin annotation-based API.
- Official
Issues Deduplication
JetBrains/ideavim
Handles deduplication of YouTrack issues. An agent skill from JetBrains/ideavim.
Related
Works with
Categories
Questions about Git Workflow
What does Git Workflow do?
IdeaVim git workflow conventions covering commits, branches, PRs, and CI. Git Workflow is an agent skill from JetBrains/ideavim, published by the product's own GitHub organization. IdeaVim git workflow conventions covering commits, branches, PRs, and CI.
When should I use Git Workflow?
Git Workflow fits situations like: creating commits; managing branches; creating pull requests; reviewing git history.
How do I install Git Workflow in Claude Code?
Run `npx skills add JetBrains/ideavim --skill git-workflow -a claude-code`. Or copy the skill folder (.claude/skills/git-workflow in JetBrains/ideavim) into .claude/skills/git-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Git Workflow in Codex?
Run `npx skills add JetBrains/ideavim --skill git-workflow -a codex`. Or copy the skill folder (.claude/skills/git-workflow in JetBrains/ideavim) into .agents/skills/git-workflow in your project. Codex loads it when a task matches its description.
Can I use Git Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JetBrains/ideavim --skill git-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-workflow, .gemini/skills/git-workflow, .github/skills/git-workflow and .opencode/skills/git-workflow in your project.
What does Git Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Git Workflow is instructions for the agent only.
Does Git Workflow access the network?
SKILL.md names 1 domain. As links in the text: youtrack.jetbrains.com. This is read from the text; nothing was executed.
Is Git Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Git Workflow use?
Git Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Git Workflow use?
About 424 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Git Workflow?
Skills that share tags, products or a category with Git Workflow: Git GitHub Ops (c5inco/compose-pokedexer, 143 stars), Finishing a Development Branch (obra/superpowers, 296k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Git Workflow?
JetBrains (a GitHub organization, an official publisher) maintains it in JetBrains/ideavim, which has 10,278 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.
Source: JetBrains/ideavim on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.