GigaCode Commit plugin
gigacode-commit
IntelliJ IDEA plugin that writes a Git commit message from selected changes through the local GigaCode or Codex CLI agents
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- The selected diff goes to the local CLI agent process in full
- The plugin runs external commands with configured arguments
Install
- Works in
- Services
Manual install
mvn clean verifyBuilds the plugin ZIP, then `Install Plugin from Disk`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The selected diff goes to the local CLI agent process in full
- The plugin runs external commands with configured arguments
This is third-party code. Review the repository files before installing.
What it does
The plugin adds a message generation button to the Commit panel of IntelliJ IDEA. A developer ticks files, the plugin builds a diff for the selected changes only and hands it to a local `gigacode` or `codex` CLI agent. The agent returns a subject and a body, the plugin applies a template and pastes the text into the message field. No commit is made automatically and the text stays editable. Each agent has its own CLI profile with an argument table of "enabled, key, value". The prompt goes through STDIN, an argument or a temporary file, and the answer is read from stdout or a file, as plain text or JSON with `subject` and `body` fields. Separate templates control the prompt and the final message, and language (Russian or English), subject form and detail level are set in settings. The plugin stores no API keys and adds no files the user did not select. It builds with Maven and a ready ZIP installs from a release.
Who it is for. Developers on IntelliJ IDEA who have GigaCode CLI available in an internal environment and want consistent commit messages without copying a diff into a chat.
Good fit when
- Before committing a large change you want a subject and body from the diff in one click
- The team agreed on a message format and the template sets one look for subject and body
- Code must not go to an external service, so analysis runs through a local agent
- Messages are kept in Russian or English depending on the project
Not a fit when
- Neither `gigacode` nor `codex` is installed and signed in on the machine: the plugin calls only them
- The IDE is not IntelliJ IDEA on platform build 253 or newer
- A commit must be created with no human involved: the plugin only fills the text field
Example request
Generate a commit message for the selected files: a subject up to 72 characters and a short body in Russian.Limitations
IntelliJ IDEA 2025.3.3 or a compatible IDE on platform build 253.31033.144 and newer is required, along with the Git plugin from the standard bundle and an installed agent in `PATH` or an absolute path to it. Building from source needs JDK 21 and Maven 3.9.
Message quality depends on the chosen agent and the prompt template. The plugin makes no commit and sends no unselected files, but the selected diff goes to the agent process in full. Installation is from a ZIP: `Settings`, `Plugins`, `Install Plugin from Disk`. The repository carries no license.
How to disable. Disable or uninstall the plugin in `Settings`, `Plugins`, then restart the IDE.
FAQ
How do I install the GigaCode Commit plugin in IntelliJ IDEA?
Build a ZIP with `mvn clean verify` or download a ready one from a release, then choose `Install Plugin from Disk` in the plugin settings and restart the IDE.
Which agents does the plugin support?
The local `gigacode` and `codex` CLIs. Each has its own editable profile with arguments and a prompt delivery method.
Does the plugin send all changes to the agent?
No. Only files ticked in the Commit panel go into the request, including ticked untracked ones.
Does the plugin make the commit itself?
No. It pastes a subject and body into the message field, then a person edits the text and confirms the commit.
Can I change the language and subject form?
Yes. Settings let you choose Russian or English, the grammatical form of the subject and one of three detail levels.
Discussion
No questions or reviews yet.
Related
All GigaChat toolsGigacode Task Commit Check
gigaide-precommit-gigacode
GigaIDE and JetBrains plugin that runs chosen GigaCode CLI tasks before a commit with the change context passed as JSON
Process Kit for GigaCode
process-kit
A GigaCode workspace where the assistant takes a task in words, finds a ready process made of steps and runs it with a plan and a report in outputs
GigaCode Bridge MCP
Gigacode-bridge-mcp
MCP server that delegates isolated code edits to GigaCode CLI in temporary Git worktrees and returns a patch for independent review
GigaCode project flows with hooks, gates and OpenSpec
gigacodeAgents
A monorepo of flows for the GigaCode CLI: development with stages and hard gates, a work progress observer and reverse analysis of code into a spec
A single Node.js file turns the installed GigaCode CLI into a local OpenAI server with streaming and a shared dialogue history
Eight skills for coding against the GigaChat API: choosing a layer, access setup, SDK, LangChain, gpt2giga and Deep Agents
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| GigaCode Commit (this card) | no | 0 | |
| Conventional Commit Message skill for agents | yes | 8,527 | a conventional-message skill without IDE integration |
| aicommits | no | 9,125 | a console CLI for commit messages without an IntelliJ panel |
README in short
The README covers the purpose, features, the generation flow, requirements, ZIP installation, settings and CLI profiles, templates, plugin architecture, building and error diagnostics.