hyperflow-cache
Hyperflow memory manager. Use to view, search, add, edit, prune, or clear hyperflow project memory — "show memory", "search memory for X", "clear memory", "what does hyperflow remember about Y". CRUD over .hyperflow/memory/ only — never touches source code.
Allowed Tools
No tools specified
Provided by Plugin
hyperflow
Point it at a GitHub issue and get back a reviewed pull request. Hyperflow turns one AI coding session into a structured engineering pipeline: plan sharpens and decomposes the work, dispatch fans out parallel workers, and a domain specialist reviews every step — nothing ships unreviewed. 18 skills, 22 specialist reviewer and investigator agents, adaptive depth so a 5-line fix never triggers a deep run, and persistent per-project memory that lives in your repo and never leaves it. Runs on whatever model your session already uses — zero config, no API keys, no daemon. Works across Claude Code, Codex App/CLI, OpenCode, Grok, Antigravity, and Cursor.
Installation
This skill is included in the hyperflow plugin:
/plugin install hyperflow@claude-code-plugins-plusClick to copy
Instructions
hyperflow-cache — memory CRUD (Antigravity single-agent)
Manage .hyperflow/memory/ entries. Only memory files — never source code. Follow the hyperflow doctrine.
Operations
- view / list — print the entries in
.hyperflow/memory/{decisions,learnings,pitfalls,patterns}.md. - search
- add — append a tagged entry to the right category file (decisions / learnings / pitfalls / patterns). Use the format:
##then-.(recorded ) - edit
- prune / clear — remove stale or wrong entries. Confirm via AskUserQuestion before a destructive clear (binary Yes/No).
Rules
- Scope is
.hyperflow/memory/only. Don't record what the repo/git already captures; record the non-obvious why.