> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/aviator-cli/manpages/av-commit-1.md).

# av-commit-create(1) in CL

Find information about the av-commit-create(1) command in manual pages for Stacked PRs CLI. Synopsis, description, and options in Aviator Documentation.

### NAME

av-commit - Record changes to the repository with commits

### SYNOPSIS

```synopsis
av commit [-m <msg>| --message=<msg>] [-a | --all] [--amend] [--edit]
    [-b | --branch] [-A | --all-changes] [--branch-name <name>]
    [--parent <parent_branch>]
```

### DESCRIPTION

Create a new commit containing the current contents of the index and the given log message describing the changes, then run **av restack** on all subsequent child branches with the new commit.

Previous to running **av commit**, add changes to the index via git-add(1) to incrementally "add" changes to the index.

### OPTIONS

`-m <msg>, --message=<msg>` : Use the given `<msg>` as the commit message.

`-a, --all` : Automatically stage modified/deleted files, but new files you have not told Git about are not affected. (Same as git commit --all)

`-A, --all-changes` : Automatically stage all files, including untracked files

`--amend` : Amend the last commit, using the same message as last commit by default

`--edit` : When amending a commit, open the default git `$EDITOR` for modifying the commit message

`-b, --branch` : Create a new branch with an automatically generated name and commit to it

`--branch-name <name>` : Create a new branch with the given name and commit to it

`--parent <parent_branch>` : Instead of creating a new branch from current branch, create it from specified `<parent_branch>`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aviator.co/aviator-cli/manpages/av-commit-1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.