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

How to upgrade an older memory install and keep your own edits with AI Memory Skillpack

Move a machine to a newer pack while receipt hashes protect edited files.

Who it is forA developer or team lead with an older pack already installed on a machine who needs the newer version without losing local changes.

The problemA naive upgrade can overwrite memory files the user edited by hand, silently losing project knowledge.

The outcomeFiles the pack did not change are updated, edited files are kept and reported, and the old pack is archived rather than destroyed.

What you need first

  • Linux or WSL with bash 4.4 or newer, git, rg, and sha256sum
  • Codex CLI installed on the machine
  • Optional: Claude Code, which uses the same skill source through symlinks
  • Optional: Python 3.10 or newer, only for project-mastery-coach
  • macOS needs GNU sha256sum, flock, readlink -f, and a newer bash, or the installer stops

Steps

  1. Read the migration/ folder in the new pack to find the procedure for machines with an older pack
  2. Run sha256sum -c SHA256SUMS in the new pack and confirm all lines report OK
  3. Tell Codex: Read INSTALL.md in this pack and follow the upgrade or migrate path for this machine.
  4. Review the receipt report for any file whose hash mismatched, and confirm your edits were kept
  5. Confirm the old pack was archived, not deleted, before you remove anything by hand

Prompt for your agent

In the new ai-memory-skillpack checkout, follow INSTALL.md and the migration/ procedure to upgrade the memory install on this machine. Expected output: a list of files replaced, files kept because of local edits, and the archive path of the old pack. Verify that no file with a receipt hash mismatch was overwritten.

Caveat. The README says the installer targets bash 4.4 or newer and GNU tools, so an older bash or a stock macOS shell will stop the upgrade before any file changes.

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