Short steps
One task in a few steps, or 5 quick things to try with one tool. Everything comes from the official docs, linked on each page.
Copilot went one step too far? Roll the session back to an earlier prompt and, if you like, put back the files Copilot changed.
Source: GitHub Docs: roll back changes in Copilot CLI · GitHub Docs: plans for GitHub Copilot
Typing the same instructions to goose again and again? Put them in a .goosehints file once and goose picks them up every session.
Tired of repeating how you like your answers? Save them once; Copilot Chat on GitHub uses them every time.
Source: GitHub Docs: add personal custom instructions · GitHub Docs: plans for GitHub Copilot
Explaining your build commands to Claude Code every session? Write them into a CLAUDE.md once and Claude reads it at the start of every session.
Source: Claude Code docs: how Claude remembers your project · Claude Code docs: account requirements
Write your repo’s rules down once and Copilot adds them to requests in that repository. One Markdown file in .github carries how to build, test and style changes in that repository.
Source: GitHub Docs: Adding repository custom instructions for GitHub Copilot
Want more out of a Copilot CLI session? Try these five slash commands next time you open one.
Source: GitHub Docs: Copilot CLI command reference · GitHub Docs: managing context for Copilot · Copilot CLI changelog · GitHub Docs: plans for GitHub Copilot