DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to reopen a saved tour without waiting for the LLM again with Diff Tour

Return to a change you toured earlier and open its saved tour instantly.

Who it is forA reviewer who stepped away from a branch and wants to pick up the same tour later without paying the wait again.

The problemWriting a tour takes 2 to 5 minutes, which is slow when you only want to reread it.

The outcomeThe saved tour for the change opens right away, and you can keep stepping through it where you left off.

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

  1. Run cd your-repo
  2. Run tour
  3. Pick the same change from the list again (inferred, check the README)
  4. Press → and ← to step through, and q to quit

Prompt for your agent

In the repository at <path>, open the saved tour for the branch <branch> with tour. Expected output: the tour opens without the writing step. Verify with `git status` that the repository is unchanged.

Caveat. The README says the finished tour is saved in your cache, but it does not say when a saved tour is refreshed, so a change made after the tour was written may not appear.

Share: 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