Skip to content
Sign in

ghola

A starter kit for agentic systems on iii: a spec goes in, a pull request comes out, nothing merges itself. The stage-graph factory, the constraint ladder and the append-only audit log, wired as registry workers, with the operator profile and skills to run them.

InstallLatest

# With the iii engine running

iii trigger directory::download-kit kit=tacoda/ghola
0Installs
0Last 7 days
0Today
30 days

Exact versions are immutable. Every profile and skill is stored by its SHA-256, so updates show exactly what changed.

Skill ID
tacoda/ghola/run-the-tests
Used by
ghola

Skill

1,404 bytes

run-the-tests

skills/run-the-tests.md

Run the tests

make test

No engine, no key, no money. It reads tests/ and nothing else, so it works on a fresh clone before make setup has finished thinking about your toolchain.

Reading a failure

The test names are sentences and the docstrings carry the bug each one prevents, so a failing name usually says what broke without opening the file. Two classes of failure mean something specific:

  • test_docs fails when a page names a make target that does not exist, links to a missing file, or a prompt names a field the factory does not supply. It is a documentation failure, not a code one.
  • A count in a docstring or in README.md is not checked by anything. If you add tests, update README.md, which states the number.

When it passes and you still are not done

make test sends no turn, so it proves nothing about a prompt. make eval does, and it costs money. docs/EVALS.md says when to run it; the short answer is before any change to prompts/.

make test-live is the other suite: framework contract tests against a running engine (make up first). It is the only kind of test that catches a framework change — the harness ignoring a hook's deny was found by exactly one of these.

Search the registry

Find workers, kits and executables, or jump to a page.