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

How to find the edit that broke a test and restore the file with My Claude Code Mods

Use Time Machine's step timeline and shadow-git snapshots to locate and undo a breaking edit.

Credentials. Shadow-git snapshots store file states, so any secrets in tracked files may be captured in the recorder store.

Who it is forA developer whose test suite went from passing to failing during an agent session and who needs to know which change caused it.

The problemAfter many tool calls, it is hard to tell which edit introduced a failure or what the files looked like before it.

The outcomeThe specific step that broke the test, the file as it was at an earlier step, and a restored state you can re-test.

What you need first

  • A Claude Code CLI with Mods support (mods are enabled by default from 2.1.287)
  • git on your PATH for Time Machine
  • A terminal running macOS, Linux, or a Bash or Zsh shell for the install block
  • Node 22.19.0 or later only if you plan to run the repo's development tests

Steps

  1. Confirm git is on your PATH (inferred: git --version). (inferred, check the README)
  2. Add the marketplace with claude plugin marketplace add YeonwooSung/my-claude-code-mods if you have not already.
  3. Install with claude plugin install time-machine@my-claude-code-mods --scope user.
  4. Start a new Claude Code session, or run /reload-plugins, then run /plugin to confirm time-machine is loaded.
  5. Open the timeline, view the files as they were before the failing step, and restore that state; then re-run your test command.

Prompt for your agent

In the repo YeonwooSung/my-claude-code-mods, install time-machine at user scope, then after a failing run of <test command> identify the tool call that introduced the failure. Output the step number, the file changed, and the restored content for that file. Verify the result by re-running <test command> after the restore and reporting pass or fail.

Caveat. The README says Time Machine needs git on your PATH and that its per-test options are ignored on the early-access 2.1.280 build.

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