一键导入
remember
Save a decision, gotcha, or architectural choice to the Obsidian vault. User-initiated only.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Save a decision, gotcha, or architectural choice to the Obsidian vault. User-initiated only.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Build, install, run, and test the claude-dev-env installer. Use when asked to run claude-dev-env, install the Claude Code config into ~/.claude, drive the installer, smoke-test it against a sandbox, or run its test suite.
Max-recall code review at a selectable effort level (low, medium, xhigh), with optional auto-fix and an auto-execute loop for any level. Triggers: /e-code-review, /e-code-review low, /e-code-review medium, /e-code-review xhigh, /e-code-review <level> --fix, /e-code-review <level> loop.
Build a polished self-contained HTML product launch and release-notes page from work completed in the current session, using available repository state, source-of-truth files, tests, approvals, artifacts, commits, pull requests, previews, and release evidence. Use when the user asks to build release notes, create a launch page, document completed work, produce feature-release HTML, or turn the session into product-facing release notes.
File, update, and close GitHub work as one epic with native sub-issues. Dedup open and closed issues first. Edit status only inside marker sections. Refresh the epic checklist so it matches its children. Triggers: issue tracker, file an issue, track this issue, open an epic, update the epic, close the issue, refresh the epic checklist, attach a sub-issue.
Harvests session obstacles into GitHub issues backed by quoted evidence: validates each draft with the user, then delegates filing to the issue-tracker agent (skill fallback), which dedupes against open and closed issues and files each under an epic as a native sub-issue. Prints a cloud handoff prompt. Triggers: /closeout, close out this session, close out the session, file the session obstacles, session closeout, harvest session obstacles, end-of-session issue filing. Not session-log (vault journal) — closeout files issues and writes no journal.
Cleanup-only pass on the current diff — reuse, simplification, efficiency, altitude — that fixes what it finds directly; no correctness-bug hunting. Triggers: /e-simplify.
| name | remember |
| description | Save a decision, gotcha, or architectural choice to the Obsidian vault. User-initiated only. |
| disable-model-invocation | true |
| argument-hint | [what to remember] |
Save a structured decision, gotcha, or architectural choice to the Obsidian vault as an individual note in the decisions/ directory.
Parse the input. Extract the core decision, fact, or gotcha from $ARGUMENTS.
Classify the type based on content:
decision -- a choice made between alternatives (e.g., "chose Groq over Gemini")procedural -- a how-to or workflow step (e.g., "deploy requires manual cookie refresh first")fact -- an objective piece of information (e.g., "YNAB API cannot overwrite split transactions")gotcha -- a surprising behavior or trap (e.g., "Amazon blocks Cloud Run datacenter IPs")Infer the project name from conversation context (git remote, working directory, or topic).
Generate a short title (3-7 words) that captures the essence.
Write to vault via mcp__obsidian__write_note:
Path: decisions/[Project] - [Short Title].md
Frontmatter:
name: [Short Title from step 4]
description: [One-line summary of the decision/fact/gotcha -- concise enough for frontmatter search]
type: [decision|procedural|fact|gotcha]
project: [Project Name]
date: [YYYY-MM-DD]
status: Active
tags: [relevant, tags]
Body format depends on type:
For decision:
**Decision:** [One sentence stating what was decided]
**Reasoning:** [Why this was chosen]
**Alternatives considered:** [What was rejected and why]
**Consequences:** [What this means going forward]
For gotcha:
**Gotcha:** [One sentence stating the surprising behavior]
**Symptom:** [What you observe when you hit this]
**Fix:** [How to work around or resolve it]
For fact or procedural:
[The fact or procedure, written clearly in 1-3 sentences with relevant context]
Confirm what was saved and where (vault path).