SkillFoxx

Type a name, a task or a service

Match with Foxx AI

Gigacode Task Commit Check plugin

gigaide-precommit-gigacode

GigaIDE and JetBrains plugin that runs chosen GigaCode CLI tasks before a commit with the change context passed as JSON

  • 0 ★ on the repository
  • Last commit
Plugin

Extended access

Why this level

  • The plugin runs an external command before every commit with paths and the commit message
  • Tasks are executed by a local agent and its actions depend on the task text
All reasons and checks
Russian stack

sorface/gigaide-precommit-gigacodeAuthor:sorface

Install

Works in
Services

Manual install

mvn package

Builds the ZIP in `target/`.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The plugin runs an external command before every commit with paths and the commit message
  • Tasks are executed by a local agent and its actions depend on the task text

This is third-party code. Review the repository files before installing.

What it does

The plugin adds a "Gigacode tasks" check to the Commit window. A user creates tasks with a name and description, enables the needed ones, and before a commit the plugin runs each in turn with `gigacode task run --context <file>`. The context goes through a temporary JSON file. The context holds the task name and description, the project root, the commit message, a list of changed files with relative and absolute path, change type, VCS root and module name, and the affected modules. This way the local GigaCode agent sees what changes and performs a check such as a review or a search for missing tests. Settings live in `Settings`, `Tools`, `Gigacode Commit Check`, where the plugin also verifies that the `gigacode` CLI is available. The check is turned on in the Commit window. Installation is a ZIP from the GitHub release via `Install Plugin from Disk`, and building uses `mvn package`.

Who it is for. Teams on GigaIDE or IntelliJ who want their own GigaCode-driven checks inside the commit flow: review, tests, style rules.

Good fit when

  • Every commit goes through an automatic review by a local GigaCode agent before it is sent
  • Several tasks cover different rules and some are enabled only for a release
  • The agent needs to know the affected modules so the check covers the right parts of a monorepo
  • The team works in an internal environment where only the local GigaCode CLI is available

Not a fit when

  • The team does not use GigaCode CLI: the plugin runs only it
  • A check has to block a commit with a hard server rule: the plugin works locally in the IDE
  • Tasks are written on the fly for a one-off question, an ordinary agent chat is enough for that

Example request

Create a "pre-commit review" task: check the diff for forgotten debug calls and report the list of files.

Limitations

The plugin runs `gigacode task run`, so an installed and configured GigaCode CLI is needed on the machine. The README names no IDE versions the plugin was verified with, and no license is visible in the repository.

The plugin passes paths and the commit message to the agent, so the result depends on what the task itself does: execution, answer formats and exit codes are set by the user. Building goes through Maven and CI publishes a ready ZIP to GitHub releases. The last push to the repository dates from August 2026.

How to disable. Turn the check off in the Commit window or uninstall the plugin in `Settings`, `Plugins`.

FAQ

How do I install the plugin in GigaIDE?

Download the ZIP from the GitHub release and choose `Install Plugin from Disk` in plugin settings, or build a ZIP with `mvn package`.

What does a task receive as input?

A temporary JSON with the task name and description, the project root, the commit message, the list of changed files and the affected modules.

Which command runs a task?

`gigacode task run --context <file>`, where the file holds the change context. Tasks run one after another.

Where do I turn the check on?

Tasks are created in `Settings`, `Tools`, `Gigacode Commit Check`, and the check itself is turned on in the Commit window.

Does the plugin work without GigaCode CLI?

No. The plugin only launches the CLI and hands it the context, and the agent performs the check.

Discussion

No questions or reviews yet.

All GigaChat tools

GigaCode Commit

gigacode-commit

Russian stack

IntelliJ IDEA plugin that writes a Git commit message from selected changes through the local GigaCode or Codex CLI agents

PluginExtended access
Russian stack

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

WorkflowExtended access

GigaCode Bridge MCP

Gigacode-bridge-mcp

Russian stack

MCP server that delegates isolated code edits to GigaCode CLI in temporary Git worktrees and returns a patch for independent review

MCP serverExtended access

README in short

The README briefly describes the context tasks receive, building through Maven, ZIP installation from a release and task setup in the Commit window.

README badge

Report a problem

Foxx AIGigacode Task Commit Check
Foxx AI

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.