> 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/how-to-guides/navigating-and-modifying-stacked-prs.md). # How to Navigate & Modify Stacked PRs ### Visualizing a stack Run the command ``` av tree ``` to print out a visualization of the current PR stack. ### Navigating a stack Since a stack is (conceptually) a sequence of branches, navigating between different parts of the stack is as simple as running `git switch `. You can also use `av switch` to interactively switch the branches. Or you can use `av prev` and `av next` to navigate through branches in order. ### Adding a commit to a branch within a stack First, checkout the branch you want to add a commit to with ``` git checkout "" ``` (note that after you commit, subsequent branches in the stack will also contain this commit). Modify the repository using your normal development workflow, and when you're done, stage and add the changes: ``` av commit -a -m "" ``` `av commit` will automatically rebase all of the commits in the stack to include the new commit, without pushing them to GitHub. If instead you run `git commit` you can always resync the stack with `av restack`. To rebase and push your changes to GitHub run ``` av sync ``` --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.aviator.co/aviator-cli/how-to-guides/navigating-and-modifying-stacked-prs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.