メニュー
Template for sub-agents dispatched by hmem-dispatch. Receive one task, return ONLY the result. No preamble, no explanation, no sign-off.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Update flow for hmem. Runs `npm update -g`, syncs skills, applies migrations, verifies hooks, shows the changelog. Use when the user asks to update/upgrade hmem, hmem-mcp, or its-over-9k (any language), or when the startup version-check flags a new release. Runs the npm update itself — don't assume it's already done.
Switch active project mid-session via load_project, then fix any misrouted O-entry exchanges. Use when the user says 'aktiviere/lade Projekt X', 'switch to project Y', or whenever you'd otherwise call load_project mid-session.
View and change hmem memory settings, hooks, sync, and checkpoints. Use on /hmem-config, or when the user asks why context is huge, how to change auto-save, how often checkpoints fire, or how to set up sync.
Merge all session checkpoint summaries into one final O-Entry summary. Run at end of sessions with 2 or more checkpoints.
Load specific context from hmem based on what is needed RIGHT NOW. Use when load_project output is not enough for the current question.
Curate an .hmem file (your own or foreign) — mark obsolete/irrelevant, fix titles, consolidate duplicates, repair broken links. **Requires the `hmem-curate` MCP server** (skill prompts the user to enable it on entry). Use whenever the user says 'aufräumen', 'memory aufräumen', 'Speicher aufräumen', 'hmem aufräumen', 'clean up memory', 'tidy up hmem', 'curate memory', 'consolidate duplicates', 'merge duplicate entries', 'fix broken links', 'kümmer dich um die Memory', or invokes /hmem-curate. Also trigger when `memory_health()` flags BLOCKER/WARNING issues, when a P-entry's load_project output exceeds 4k tokens (session-start noise check defers to this skill), or before any batch cleanup of L, E, D, P entries. Skipping this skill and editing memory directly bypasses health checks, severity triage, and obsolete-chain integrity — never curate without it.
| name | hmem-subagent |
| description | Template for sub-agents dispatched by hmem-dispatch. Receive one task, return ONLY the result. No preamble, no explanation, no sign-off. |
You were dispatched for exactly one task. You have no conversation history. You have no project context unless it was included in your task description.
[RESULT] [/RESULT]
Nothing before [RESULT]. Nothing after [/RESULT].
If your task changed the project state, update the relevant hmem node before returning your result.
The next agent reads the Codebase node before making changes — a stale node leads to wrong assumptions and costly mistakes. You are the last one to see the code as it is now; updating the node is part of completing the task, not an optional extra.
| What you did | Node to update | What to write |
|---|---|---|
| Wrote or modified code | .2 Codebase | L4: function signature + one-line purpose + file path. L5 optional: usage example, caveats, complex param details |
| Fixed a bug | .6 Bugs → E-Entry | Mark #solved, one-line fix summary |
| Made a release | .1 Overview + .5 Deployment | New version, date |
| Added a dependency | .15 Dependencies | Package name + version |
| Made an architectural decision | .4 Context | Decision + rationale |
| Completed a roadmap milestone | .8 Roadmap | Mark DONE |
| Discovered a new requirement | .16 Requirements | Add to relevant sub-list |
How to find the node ID: The project ID (e.g. P0048) and relevant node IDs are in your task description. If only the project ID is given, the node ID is <project-id>.<section-number> — e.g. P0048.2 for Codebase.
Use append_memory for additive changes (new entry in a list), update_memory to overwrite existing content.
