Skip to content
git-acm logo docs

commands reference

this document serves as a reference for all commands available in git-acm, including their syntax, parameters, expected outputs, and examples.

core commands

Section titled “core commands”

fetch models run once

Section titled “fetch models ”
Terminal window
git-acm get-models
  • description: fetches models from OpenRouter and stores them locally.
  • expected output: installation progress and success message.

configuration commands

Section titled “configuration commands”

set model required

Section titled “set model ”
Terminal window
git-acm use <model_id>
  • description: selects a model by id (copy from OpenRouter models page or git-acm list).
  • parameters:
    • <model_id>: for example, anthropic/claude-3.7-sonnet.
  • expected output: confirmation of the selected model.

enable auto-commit optional

Section titled “enable auto-commit ”
Terminal window
git-acm autocommit enable
  • description: enables the auto-commit feature.
  • parameters: none.
  • expected output: confirmation that auto-commit is enabled.

disable auto-commit

Section titled “disable auto-commit”
Terminal window
git-acm autocommit disable
  • description: disables the auto-commit feature.
  • parameters: none.
  • expected output: confirmation that auto-commit is disabled.

usage

Section titled “usage”

generate commit message

Section titled “generate commit message”
Terminal window
git-acm
  • description: generates a commit message using the selected model based on the changes in your code.
  • parameters: none.
  • expected output: a generated commit message (also copied to clipboard).

list cached models

Section titled “list cached models”
Terminal window
git-acm list
  • description: lists locally cached models fetched via get-models.
  • parameters: none.
  • expected output: a list of models.

help

Section titled “help”
Terminal window
git-acm help
  • description: displays the help menu for git-acm.
  • parameters: none.
  • expected output: a list of available commands and their descriptions.

error messages and troubleshooting

Section titled “error messages and troubleshooting”

  • error: invalid api provider

    • message: “error: unsupported api provider. please use one of: gemini, openai, anthropic, llama.”
    • solution: ensure you are using a valid api provider name.

  • error: api key missing

    • message: “error: api key is not set. please configure your api key in the .env file.”
    • solution: check your .env file for the correct api key configuration.

technical specifications

Section titled “technical specifications”
  • supported platforms: linux, macos, windows (via wsl).
  • dependencies: requires git and rust (for cargo installation).