averlo-code-replay

Installation
SKILL.md

Averlo Code Replay

This skill includes its renderer beside this file. Resolve paths from this skill directory; do not depend on an author's local checkout or a Studio account. Read README.md for setup and options.

Update before every use

The public upstream is https://github.com/olafBobryk/averlo-tool-code-replay.git, branch main. No login, token or Averlo update key is required. Before EVERY use, reuse the existing matching source checkout, inspect its branch, commits and local changes, fetch upstream main, and review incoming commits and their actual diff. Never push to Averlo's source repository.

Fast-forward only when clean and safe. Preserve local commits and customizations; never reset, clean, overwrite or automatically stash them. Ask the user how to integrate changes when their work prevents a safe update. If fetching or integration fails, explain the blocker before rendering; do not silently claim an old copy is current.

Announce a concise changelog from the last successfully integrated upstream revision to the new revision, using the actual log and diff. On first use announce the starting revision; if unchanged say no updates were found. Keep the last integrated revision in a local state file outside the checkout, for example ~/.config/averlo/tools/code-replay-state.json. Advance it only after successful integration. Announce available but unintegrated changes separately.

An installed skill may have no .git directory. Verify the repository root AND remote before Git operations so an unrelated ancestor project is never mistaken for this tool. If necessary, clone the public upstream into a dedicated source directory outside the installed skill, reuse that checkout on later runs, and render from it. Refresh an installed copy from the updated source or with npx skills update, inspecting and preserving installed customizations first. Verify the refreshed runtime matches the integrated revision before using it.

Render

Installs
2
First Seen
3 days ago