gma CLI

The gma CLI is published to npm as the gitmyabi package. It generates a typed-ABI npm package (viem) from your contract artifacts and can publish that package to any npm registry, with or without a GitMyABI account.

Two binaries are installed and point at the same entry: gma (primary) and forge-gma (Foundry-flavored alias).

When to use the CLI

• Local codegen and publishing. gma init, gma generate, and gma publish run entirely on your machine and only need a normal npm registry token to publish. No GitMyABI account is required.
• CI workflows. The same commands run in GitHub Actions or any other CI runner; see the GitHub Action guide.
• Scripting the GitMyABI platform. After gma login, the CLI unlocks gma shell and top-level groups for teams, projects, builds, repos, and ABIs — the same surface as the web app, scriptable from the terminal.

Available without sign-in

• gma init — create a gma.config.json in the current directory.
• gma generate — build a .tgz bindings tarball from your ABIs.
• gma publish — upload a tarball to an npm registry with your own token.
• gma demo — interactive walkthrough with mocked output.
• gma login — sign in to GitMyABI via GitHub OAuth.

Available after sign-in

• gma whoami, gma logout — inspect or clear the stored profile.
• gma shell — interactive REPL covering teams, projects, builds, repos, ABIs, and the session dashboard.
• gma team, gma project, gma build, gma repo, gma abi, gma session — scriptable top-level groups that mirror the shell.

Run gma <command> --help for the full flag list of any command.