GigaCode project flows with hooks, gates and OpenSpec workflow
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
- 0 ★ on the repository
- Last commit
Extended access
Why this level
- Hooks run scripts and block agent commands on your computer, and a rule error can stop work or let a dangerous action through
- The branch is pre-release and the known enforcement limitations remain open
Install
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add workflows/gigacodeagentsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Hooks run scripts and block agent commands on your computer, and a rule error can stop work or let a dangerous action through
- The branch is pre-release and the known enforcement limitations remain open
This is third-party code. Review the repository files before installing.
What it does
A monorepo of project flows for the GigaCode CLI where hooks turn an ordinary session into a managed process. The development module (`modules/development/`) gives the `/develop-feature` and `/fix-bug` commands and runs work through the intake, contract, implement and delivery stages with an OpenSpec plan and human checkpoints (`confirm.py`, agent self-approval is closed). Deterministic gates (git-safety, spec structure, linter, build) block while heuristics only hint, and delivery opens only on a machine verdict `pass`. The analytics module (`modules/analytics/`) does reverse analysis of one business feature from code: a technical layer, an OpenSpec spec and a documentation tree. The `observer.py` web panel at `http://127.0.0.1:8787` follows the work. Hooks are run by the cross-platform launcher `node .gigacode/hooks/run-hook.cjs`.
Who it is for. Teams developing with the Sber GigaCode CLI who want to pin the development process with gates and stages instead of trusting a session on its word.
Good fit when
- The agent has to carry a feature through stages with verifiable checkpoints and mandatory human confirmation
- Repository edits must be protected: git-safety blocks dangerous agent operations
- Legacy business logic needs an OpenSpec spec assembled from code
- You want to watch the agent progress in a web panel in real time
Not a fit when
- The agent runs in Claude Code or Cursor: the hooks and commands are written for the GigaCode runtime
- You need production-ready protection: the branch is marked pre-release and has known enforcement limitations
- You need a simple set of skills: this is a whole process with stages and verdicts and you must tune it to your stack yourself
Example request
Run `/develop-feature` for the task "add a date filter to the report" and carry it through the stages with checkpointsLimitations
The repository is marked UNSTABLE and pre-release: critical bugs found by the audit are closed, but the known enforcement limitations are described in `docs/enforcement-limitations.md` and it is not recommended for production without review. The GigaCode CLI, Git, Python 3 and Node.js are required, and `quality-gates.json` is tuned to your stack. The OpenSpec CLI, Serena, Graphify and Context7 are optional. The process language is Russian by default. No license is stated in the repository, zero stars, last commit in August 2026.
How to disable. Close the project opened as the module root and delete the module `.gigacode/` and `rules/` folders from the working project, then remove the hook entries from `settings.json`.
FAQ
What is a flow in this repository?
A self-contained module with commands, rules and hooks: it opens as the project root for `gigacode`. There are two now, development and analytics.
What are gates?
Deterministic hook checks: git-safety, spec structure, linter, build. They block a step while heuristics only hint.
Can the agent approve a checkpoint itself?
No: a human confirms checkpoints through `confirm.py` and agent self-approval is closed.
How do I watch the progress?
Run `python .gigacode/hooks/observer.py` and open `http://127.0.0.1:8787`.
What must be installed?
The GigaCode CLI, Git, Python 3 and Node.js; the OpenSpec CLI, Serena, Graphify and Context7 are optional.
Discussion
No questions or reviews yet.
Related
All GigaChat toolsThe agent writes code, people decide, and gates are held by hooks in Claude Code, Codex, Cursor, OpenCode, Qwen Code and GigaCode
A Python runner executes tasks from tasks.md one GigaCode iteration at a time, then five reviewers and a finalize pass, with a separate commit per task
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 Proxy for editors: Cline, Roo Code, Continue
GigacodeOpenaiProxy
A dependency-free proxy connects GigaCode to Cline, Roo Code, Continue and Open WebUI, repairs tool call cuts and signs in with SberID
QA Agent for the GigaCode CLI: 14 roles and 6 skills for testing
QaAgentGigacodeCli
Requirements-based testing in GigaCode: from analysis and autotest review to a conclusion, with duplicate search before a bug is filed in Jira
README in short
The README lists two flows (development and analytics), environment requirements, cross-platform hook launch, the default process language and links to the quick start, the user guide and the enforcement limitations.