When it helps
If you remember an earlier page but cannot identify the commit, inspect the history and changed files first. Configure a version’s runtime when you need to see it running in a separate copy.
Git provides the code history. Added screenshots, previews and editable release notes supply context. A commit without preview material is not automatically a runnable page.
Getting started
You need Python 3.9+ and Git. Download the portable or WorkBuddy skill from Releases, retain the complete reprise folder and let your local agent follow SKILL.md. The repository also documents a command-line installation.
Run reprise . in an existing Git project to open its local workbench. Importing a repository does not install its dependencies or run build commands; approve and configure runtime commands separately.
A practical comparison workflow
Select two actual commits and inspect the changed files and diff. Confirm the project and versions before relying on attached screenshots, previews or notes.
For a running preview, check dependencies, commands and ports, then stop the process when finished. Restore or export to a new folder or ZIP and verify the files while keeping the source repository intact.
Scope of the public version
This page describes the Git-history version available on GitHub. Unpublished local experiments are not advertised as released features. Reprise is not a hosted SaaS or automatic cloud-sync service.
Separate copies are not a container sandbox. Approved install and build commands run on your machine. Historical versions can fail to rebuild because dependencies, services or environments have changed.
The code is MIT licensed; fonts, icons and imported media keep their own terms. Application data may include private materials or model settings, so back it up privately.