hmem-wipe

Save high-value knowledge and update Next Steps before clearing conversation context.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare for conversation context clear (/clear): save high-value knowledge, update project Next Steps, then instruct user to type /clear for automatic context restoration. Invoke when the user wants to clear the conversation window — not when deleting data/entries. Triggers: "/wipe", "clear context", "wipe context", "context is full/too big/getting large", "prepare for /clear", "start fresh", "context cleanup", approaching token limit. Do NOT invoke for: deleting hmem entries, clearing terminal output, cleaning up nodes/duplicates.

Core Features & Use Cases

  • Optionally save high-value knowledge via memory checkpoints before clearing context.
  • Update Next Steps to ensure session handoff after the clear.
  • Keep the system prepared to restore critical information to resume work quickly.

Quick Start

Type /wipe to initiate the wipe process and ensure the system preserves key knowledge while preparing a clean context.

Frequently Asked Questions about hmem-wipe

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

FAQPage Schema
How do I clear conversation context without losing important project memory?

To clear conversation context without losing memory, use a wipe process that saves high-value knowledge and updates Next Steps before clearing. This ensures critical project context is preserved and can be automatically restored after clearing.

What should I do when my conversation context is getting too large and approaching the token limit?

When conversation context approaches the token limit, initiate a context wipe to checkpoint high-value knowledge and update Next Steps. This safely prepares the session for a clean clear while retaining critical project information for restoration.

How does preserving memory checkpoints work before clearing a session?

Memory checkpoints work by saving high-value knowledge and updating project Next Steps before the context clear command is executed. This mechanism ensures that critical session information is stored and ready for automated restoration once the context is wiped.

When should I use a context wipe instead of deleting memory entries?

Use a context wipe when you need to clear the conversation window and start fresh, not when you want to delete memory entries. Wiping preserves key project context and Next Steps, while deleting entries permanently removes data.

Can I update Next Steps for session handoff before clearing context?

Yes, you can update Next Steps for session handoff before clearing context. The wipe process specifically updates Next Steps and saves high-value knowledge, ensuring a clean context can resume work quickly with restored critical information.

What is the difference between clearing conversation context and deleting memory data?

Clearing conversation context wipes the active session window while preserving key memory checkpoints and Next Steps for restoration. Deleting memory data permanently removes stored entries, which is not the purpose of a context wipe operation.