jigjoy-ai

Baro — Testing skill for Claude Code

Testing community

A CLI that turns a goal into a pull request - and a sandbox for testing concurrent AI coding agents on the Mozaik runtime.

How to install Baro

This entry records only its repository, not the path inside it, so there is no exact command to give. Open jigjoy-ai/baro and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Baro does

A CLI that turns a goal into a pull request - and a sandbox for testing concurrent AI coding agents on the Mozaik runtime.

Alternatives in Testing

  • RocketSimApp — RocketSim — 30+ tools for Xcode's iOS Simulator 791 ★
  • Spy — by spylang - Enforces strict coding conventions with comprehensive testing guidelines, multiple code compilati 678 ★
  • Goal — Đóng vai Skill Architect — phỏng vấn thông minh để trích xuất quy trình từ đầu người dùng, sinh AI Skill hoàn 310 ★

README

baro

Type a goal in your repo. Walk away. Come back to a verified pull request.

[![npm version](https://img.shields.io/npm/v/baro-ai.svg?color=cb3837&logo=npm&logoColor=white)](https://www.npmjs.com/package/baro-ai) [![npm downloads](https://img.shields.io/npm/d18m/baro-ai.svg?label=downloads)](https://www.npmjs.com/package/baro-ai)

baro is an autonomous software factory. It compiles your goal into a machine-checkable contract, splits it into a DAG of stories, builds them in parallel across isolated git worktrees, and blocks every merge behind fail-closed gates — declared tests, build, an evidence critic, write-surface ownership. You review a PR the gates already accepted.

One prompt → a 33-story plan → 808 passing tests → a PR, in 71 minutes. [See a real run.](https://jigjoy.ai/blog/baro-808-nestjs-jest-tests)

Install

npm install -g baro-ai

Needs Node 20+, git, and at least one backend: the `claude` CLI (default), `codex`, or any OpenAI-compatible endpoint. `baro --doctor` checks your setup.

Use

cd your-repo
baro "Add JWT authentication with role-based access control"

That opens the TUI: intake asks only what matters, you confirm the plan, the fleet runs.

For automation, detach and follow from anywhere:

baro --headless --detach --goal-file goal.txt   # prints a run id, returns immediately
baro watch                              # follow milestone events
baro logs  --follow                     # tail the raw log
baro runs                                       # list live runs
baro stop                               # stop one

Commands

Command What it does
baro "" run a goal in the current repo (TUI)
baro --goal-file read the goal from a file
baro --headless --detach ... background run for CI/automation; prints the run id
baro watch follow a live run's milestones
baro logs [--follow] print or tail