hmem-update

Orchestrates the post-update workflow for hmem-mcp and hmem-sync after a version bump.

23|5|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/Bumblebiber/hmem --skill hmem-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hmem-update
Source: https://github.com/Bumblebiber/hmem/tree/main/skills/hmem-update
Command: npx skills add https://github.com/Bumblebiber/hmem --skill hmem-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-update steps are critical to keep hmem components aligned after a version change. This Skill provides a repeatable, documented workflow to verify versions, sync skill data, migrate entries, enforce schemas, curate O-entries, and perform smoke-tests.

Core Features & Use Cases

  • Version checks and display updates across hmem packages.
  • Skill synchronization from npm to local skills directory.
  • Entry migrations and P-entry schema enforcement.
  • O-entry curation and quality checks.
  • Smoke-test suite to verify basic functionality after update.

Quick Start

Run /hmem-update to apply the post-update steps after updating hmem.

Frequently Asked Questions about hmem-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run post-update checks to keep hmem in sync after a version bump?

To keep hmem in sync after a version bump, run a post-update workflow that covers version checks, skill synchronization, entry migration, schema enforcement, and smoke-tests. This verifies versions and syncs skill data from npm to local directories.

What does entry migration and schema enforcement do for hmem-sync updates?

Entry migration and schema enforcement during hmem-sync updates align your data structures by migrating entries and enforcing P-entry schemas. This process ensures all data conforms to the updated version requirements before executing local smoke-tests.

Can I use this workflow to sync skills from npm to my local directory?

Yes, you can use this workflow to synchronize skills from npm directly to your local skills directory. The post-update orchestration includes skill synchronization alongside version checks and O-entry curation to maintain local installation alignment.

What is the best way to handle missing hooks and configuration validation after updating hmem-mcp?

The best way to handle missing hooks and configuration validation after updating hmem-mcp is to follow the guided post-update workflow. It provides clear guidance for identifying missing hooks, validating configurations, and executing safe rollback prompts if needed.

Why does my hmem smoke-test fail after a migration, and how do I rollback safely?

Smoke-test failures after migration often stem from schema enforcement issues or un-synced skill data. The update workflow identifies these failures during the smoke-test round and provides safe rollback prompts to restore your previous configuration.