Menu
Check for the latest Recall release on GitHub and print the exact update command (check-only — does not run update.sh).
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Add a structured memory record to Recall — breadcrumb, decision, or learning
Run health checks on all Recall memory subsystems — database, MCP, hooks, embeddings
Flush current session to Recall database and capture a Library of Alexandria entry
Browse and search the Library of Alexandria — curated knowledge entries with extracted wisdom
Show recent Recall memory records across all tables or a specific table
Scout an unfamiliar codebase — memory-first repo map, key paths, tests, risks, and next steps, with a strict sensitive-data boundary
| name | recall-update |
| description | Check for the latest Recall release on GitHub and print the exact update command (check-only — does not run update.sh). |
Check whether Recall has a newer release on GitHub. This skill is
read-only — it prints the recommended next step but NEVER runs
update.sh inline. Running the update while a coding agent session is
attached can corrupt in-flight hook invocations (the recall binary
lives in the same process tree via bun link).
Reads the currently installed version via recall --version.
Fetches the latest release tag from the GitHub Releases API
(/repos/edheltzel/Recall/releases/latest — unauthenticated, 60
req/hr per IP).
If current == latest: reports "up to date" and exits.
If current is behind: prints current, latest, a short excerpt of the release notes, and the exact recipe to run the update manually:
cd <path-to-Recall> && ./update.sh
update.sh pulls, rebuilds, migrates the DB, and re-registers hooks.
Rebuilding the recall binary mid-session can leave the running hook
scripts in a half-updated state. The safe sequence is: exit the coding
agent → ./update.sh → restart it.
GitHub's unauthenticated rate limit is 60 requests/hour per IP. If you hit it, the command prints a graceful fallback pointing at the releases page: https://github.com/edheltzel/Recall/releases.
Run these steps to perform the check and produce the recipe. Prefer
running the Recall-shipped helper (./update.sh --check) if the source
directory is locatable — it implements all of the logic below.
Locate the source directory. Resolve the symlink target of the
recall binary and strip /dist/index.js to get the Recall checkout:
readlink -f "$(which recall)" | sed 's|/dist/index.js$||'
Call this RECALL_SRC.
Run the check helper. If $RECALL_SRC/update.sh exists, delegate
to it — it prints the exact recipe on its own:
cd "$RECALL_SRC" && ./update.sh --check
Its output already includes the "cd ... && ./update.sh" line. Relay it to the user and stop.
Manual path (if update.sh is not present on older installs):
Capture the current version:
recall --version
Fetch the latest release tag + body:
curl -sf https://api.github.com/repos/edheltzel/Recall/releases/latest
Parse JSON with jq -r .tag_name and jq -r .body (or with bun -e
if jq is not available).
Compare versions (strip leading v). Present the result as:
Current: vX.Y.Z
Latest: vA.B.C
Release notes (excerpt):
<first ~10 lines of body>
To apply:
cd <RECALL_SRC> && ./update.sh
Do not run ./update.sh on the user's behalf. Stop at printing
the recipe. The user runs it themselves after exiting the coding
agent.