Hypergraph-Coding-Agent-Framework: Skill for Claude Code

Clear Context

This skill clears session context to prevent cross-feature bleed and allow fresh feature cycles. It is idempotent and safe to invoke at any time.

When to use this skill

• Automatically after /hyper-audit completes (post-audit hook).
• Manually at any time to reset session context between feature cycles.
• Whenever you want to guarantee a fresh session without old conversation history contaminating the next phase.

---

How to use it

Step 1: Check Idempotency State

Read .agents/memory/activeContext.md:

• If the session_cleared flag is true: /hyper-clear has already been called in this session. Return OK (idempotent, no action needed).
• If the session_cleared flag is false or missing: Proceed to Step 2.

Step 2: Flush Conversation History

Clear conversation history by starting a new conversation in Claude Code:

1. Inform the user: "Context cleared. Starting fresh session for next feature cycle."
2. The user manually starts a new conversation thread (or you can suggest: "You may now /hyper-clear by opening a new chat window").

Specification Retained:

• spec/compiled/architecture.yml — preserved
• spec/compiled/SuperPRD.md — preserved
• spec/compiled/MiniPRD_*.md — preserved
• .agents/ framework code — preserved
• Performance metrics (heuristics, model overrides) — preserved

Session State Flushed:

• Conversation history from this context window — cleared
• Temporary working memory — cleared

Step 3: Update Idempotency Tracker

Edit .agents/memory/activeContext.md:

## Session State
- session_cleared: true
- cleared_at: [CURRENT_TIMESTAMP]
- cleared_by: /hyper-clear command

Step 4: Log Result

Output to user:

========================================
✅ CONTEXT CLEARED
========================================
Session context flushed.
Architecture.yml and spec/compiled/ retained.
Ready for next feature cycle.

Idempotency: This is a fresh clear.
(Calling /hyper-clear again will be a no-op.)
========================================