菜单
Invalidate or remove a memory entry. Use when the user says "forget that", "that memory is wrong", "remove the X memory", "/forget X". Marks the file as invalidated rather than deleting — preserves history.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | forget |
| description | Invalidate or remove a memory entry. Use when the user says "forget that", "that memory is wrong", "remove the X memory", "/forget X". Marks the file as invalidated rather than deleting — preserves history. |
| allowed-tools | Read, Edit, Grep, Bash |
| effort | fast |
Trigger phrases:
/forget [topic or file name]If the user named a file directly (e.g. /forget feedback_plan_before_edit.md), use that path.
Otherwise, run:
python tools/memory.py --search "[topic]" --top 5
Show the top result(s) and ask: "Is this the memory you want to remove? (yes / pick a number)"
Read the full file content so you can show the user what will be removed:
> **File:** [filename]
> [first 5 lines of content]
Confirm: "Mark this memory as invalidated? (yes/no)"
Add status: invalidated to the frontmatter and a one-line note at the top of the body:
Before:
---
name: some-feedback
type: feedback
---
Always do X when Y.
After:
---
name: some-feedback
type: feedback
status: invalidated
invalidated: 2026-03-31
---
> **INVALIDATED** — removed by user. Kept for history only.
Always do X when Y.
Use Edit to apply the change — never delete the file.
Find the line in MEMORY.md that references this file and remove it:
- [Title](filename.md) — description
Delete that line using Edit.
Report:
Forgotten. [filename] is marked invalidated and removed from the index.
The file is kept in memory/ for history — it will no longer load at session start.
status: invalidated frontmatter prevents future confusion but preserves the audit trailScans a real codebase and writes coding-conventions.md from what it actually finds — variable style, SQL patterns, error handling, INSERT strategy, naming. Run once on any new project to bootstrap the convention system. Triggers on "scan conventions", "generate conventions", "bootstrap conventions", "extract conventions from code", "what are the conventions".
Security audit — checks auth, SQL injection, exposed endpoints, and sensitive data. Triggers on "security check", "is this secure", "check for vulnerabilities", "check auth", "audit security", "security audit".
Use when switching environments, updating config values, or verifying URLs/settings. Triggers on "check environment", "switch to production", "update URLs", "check config", "is this prod-ready".
Use when verifying a feature works, after making changes, or before shipping. Triggers on "verify this works", "test this", "does this work", "run the checklist", "before I ship", "check this end to end".
Use when cleaning up, simplifying, or restructuring existing code without changing behavior. Triggers on "refactor", "clean up", "simplify this", "this is getting messy", "too long", "hard to read", "extract this".
Use when the user wants to review a file for bugs, antipatterns, or quality issues. Triggers on "review", "check for issues", "look for problems", "audit", "before I ship".