بنقرة واحدة
remember
Store in ferrex memory (no args = session summary, with args = store that info)
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Store in ferrex memory (no args = session summary, with args = store that info)
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Produce a read-only code review report from a diff. Runs parallel reviewers, folds their findings through adjudication and humanization, and saves the report under docs/superpowers/reviews/. Shadows the built-in /review command.
Clean up code in current branch - simplify, remove AI artifacts, challenge decisions
Save session context to ferrex before context clear
Delete ferrex memories by ID
Search ferrex memory
Audit ferrex memory health
| name | remember |
| description | Store in ferrex memory (no args = session summary, with args = store that info) |
| argument-hint | Optional info to store |
Store information in ferrex memory using the ferrex__store MCP tool.
Auto-set namespace from the git repository name (basename of the repo root, not the worktree). If not in a git repo, use the basename of the working directory.
If arguments provided, detect memory type from content:
Semantic triple — if the content is a fact, decision, or relationship:
subject, predicate, objectmemory_type: "semantic"Procedural — if the content describes a workflow, process, or how-to:
content with memory_type: "procedural"Episodic — events, errors, observations, anything else:
content with memory_type: "episodic"Always set:
namespace: git repository name (basename of the repo root, not the worktree); basename of the working directory if not in a git repoentities: at minimum the project name. Add relevant concept names (tools, modules, patterns mentioned).context: branch name, relevant file pathsconfidence: 1.0 unless the user expresses uncertaintyIf no arguments, summarize the conversation and store as episodic with entities for the project, branch, and key topics discussed.
After storing: Confirm what was stored — type, entities, namespace, and memory ID.