Who it is forA developer or AI-assisted coder who has edited files and wants a second read on the change before it is committed.
The problemUncommitted edits are easy to skim past, and the reasons for risky choices are not written down anywhere.
The outcomeA tour of the uncommitted change, including untracked files that are not ignored, showing what to fix and what is fine.
What you need first
- git installed
- One of Claude Code, Codex CLI, Gemini CLI, OpenCode or Copilot CLI, installed and signed in
- A git repository with a change to tour
Steps
- Run
cd your-repo - Run
tour - Pick the uncommitted changes from the list and press Enter (inferred from the README: uncommitted changes can be toured)
- Wait 2 to 5 minutes while the tour is written
- Press → and ← to step through, and q to quit
Prompt for your agent
In the repository at <path>, run tour on the uncommitted changes and report which files the tour points to first. Expected output: a list of file names from the tour. Verify with `git status` that the working tree is unchanged after the run.
Caveat. Only tracked files and untracked files that are not in .gitignore are sent to the LLM, so check that nothing sensitive is left unignored before you run it.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page