hmem-activate

Activate a target project with load_project and detect misrouted exchanges.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps manage mid-session project switches by activating the correct project context and detecting misrouted exchanges.

Core Features & Use Cases

  • Note the currently active project and determine OLD_PROJECT and OLD_O.
  • Activate the target project with load_project and verify O-entry routing.
  • Detect and move misrouted exchanges to the correct TARGET_O, then perform a memory cleanliness check.

Quick Start

Directly switch to the target project mid-session using load_project and verify that memory routing aligns with the new O-entry

Frequently Asked Questions about hmem-activate

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

FAQPage Schema
How do I switch AI memory projects mid-session without misrouting logs?

To switch projects mid-session, activate the target project using load_project and verify that memory routing aligns with the new O-entry to prevent misrouted exchanges.

What happens to session memory when I activate a different project context?

Activating a different project context identifies the old project, loads the target project, and moves any misrouted session nodes to ensure logs align with the new O-entry.

How do I fix misrouted exchanges after a project switch?

Fixing misrouted exchanges involves detecting logs routed to the wrong O-entry and moving the relevant session nodes to the correct target O-entry for proper memory alignment.

Can I check memory cleanliness after switching project contexts?

Yes, after switching project contexts and moving misrouted exchanges, a noise check is performed on the load_project output to report memory cleanliness and activation status.

When do I need to verify O-entry routing for session management?

You need to verify O-entry routing during mid-session project switching to ensure that memory logs and session nodes align with the newly activated target project context.

Does project switching require moving session nodes manually?

No, the project switching process automatically detects misrouted exchanges and moves relevant session nodes to the correct target O-entry, followed by a memory cleanliness check.