hmem-migrate-o

Migrate O-entries to a 5-level hierarchy and bind them to P-entries by sequence.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/YuryZZZ/opencode-global --skill hmem-migrate-o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hmem-migrate-o
Source: https://github.com/YuryZZZ/opencode-global/tree/main/skills/hmem-migrate-o
Command: npx skills add https://github.com/YuryZZZ/opencode-global --skill hmem-migrate-o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate O-entries from the old flat O-entry format to the new 5-level hierarchy, binding each O-entry to its P-entry by sequence, ensuring consistent project association and streamlined memory management.

Core Features & Use Cases

  • Bind O-entries to P-entries by matching sequence numbers (e.g., O0048 -> P0048).
  • Create non-project catch-all O/P entries (O0000 / P0000) when missing.
  • Provide a safeguarded, step-by-step migration with backups, conflict handling, and legacy tagging for traceability.
  • Verify migration state and support post-migration cleanup to keep the system healthy.

Quick Start

Run the migration after upgrading to v5.3+ and activate it via the MCP interface, then follow the on-screen prompts to complete the process.

Frequently Asked Questions about hmem-migrate-o

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

FAQPage Schema
How do I migrate O-entries to a project-bound hierarchy structure?

Migrate O-entries to a project-bound 5-level structure by matching sequence numbers to bind O-entries to P-entries, creating catch-all entries, and tagging items for traceability.

What is the 5-level O-entry migration process?

The O-entry migration process transforms old flat O-entries into a project-bound 5-level hierarchy by binding each O-entry to its corresponding P-entry by sequence, handling conflicts, and tagging legacy items for traceability.

Do I need the hmem-curate MCP server to migrate O-entries?

Yes, the O-entry migration requires the hmem-curate MCP server, specifically utilizing its move_nodes and rename_id functions to execute the structural transformation and sequence matching.

Can I run the O-entry migration before upgrading to v5.3?

No, you must upgrade to v5.3+ before running the O-entry migration, as the project-bound 5-level hierarchy transformation requires the updated system architecture to function correctly.

How does the migration handle missing P-entries or conflicts?

The migration handles missing P-entries by creating non-project catch-all O0000 and P0000 entries, while conflicts are resolved through safeguarded step-by-step processing with backups and legacy tagging for traceability.

What's the best way to verify and cleanup after O-entry migration?

After completing the O-entry migration, verify the migration state and execute post-migration cleanup through the MCP interface to ensure consistent project association and maintain healthy memory management.