Kumite

Kumite installs and configures the Pi agent coding harness for projects that use the kumite subagent workflow.

Install

Install from GitHub:

curl -fsSL https://raw.githubusercontent.com/OnishellT/kumite/main/install.sh | sh

Install and immediately run global setup:

curl -fsSL https://raw.githubusercontent.com/OnishellT/kumite/main/install.sh | KUMITE_SETUP_GLOBAL=1 sh

Install from a local checkout:

git clone https://github.com/OnishellT/kumite.git
cd kumite
./install.sh

Install from a branch or a fork:

KUMITE_REPO_REF=development \
KUMITE_REPO_URL=https://github.com/OnishellT/kumite.git \
sh -c "$(curl -fsSL https://raw.githubusercontent.com/OnishellT/kumite/main/install.sh)"

Useful installer options:

KUMITE_BIN_DIR="$HOME/.local/bin" ./install.sh
KUMITE_SETUP_GLOBAL=1 ./install.sh
KUMITE_YES=1 ./install.sh

The installer requires go on PATH. When it is not run from a checkout, it also requires git so it can clone the repository before building the kumite binary.

Daily Use

Install global Pi extensions, including pi-kumite, and static-analysis tooling:

kumite setup --global --keep-going

Kumite needs the Pi project extension pi-kumite. kumite setup --global installs it with Pi, and project initialization registers it in .pi/settings.json as npm:pi-kumite so Pi loads the Kumite orchestration extension for future sessions in that project.

Initialize a project with kumite Pi agents, skills, chain, MCP config, agents.md index, and memory docs:

cd /path/to/project
kumite init

For local extension development, use kumite init --pi-package /path/to/pi-kumite to register a local checkout instead of npm:pi-kumite.

kumite init upserts agents.md, the curated agent entry point and index for project memory. It links to deeper memory files instead of duplicating them.

Run the full setup for the current project, including global tooling and project files:

kumite setup --keep-going

Branches

• development: active integration branch. Pull requests into this branch run code quality and tests, but not release builds.
• staging: release-candidate branch. Pull requests into this branch run code quality and tests, but not release builds.
• main: release branch. Pull requests into this branch run code quality, tests, and build checks. Merges to main create a GitHub release from VERSION.

Protected branches require pull requests and passing checks before merge. See Branching And Releases.

Development Checks

Install local Git hooks:

make install-go-tools
python -m pip install pre-commit
pre-commit install

Run the same checks used by GitHub Actions:

make ci

GitHub Actions runs quality and test checks on pull requests into development, staging, and main. Pull requests into main also run build checks. After a merge to main, the release workflow builds Linux, macOS, and Windows binaries and creates a GitHub release.