> 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 Learn how to navigate and modify StackedPRs with av tree when using Aviator's CLI. ### 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 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/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 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.