cf-rememberlisted

Extract project knowledge from conversation to docs/memory — for AI recall in future sessions. Use when the user wants to save project context, capture decisions, document conventions, or preserve knowledge from the current session — e.g. "remember this", "save this to memory", "document what we did", "capture this decision", "write this down", "save for later", "don't forget", "note this", "record this convention", "preserve this knowledge". Auto-invoke when ANY of these signals appear: (1) A bug fix (via cf-fix or cf-sys-debug) involved a non-obvious root cause, a workaround, or required multiple failed attempts before resolving — save to bugs/ so future sessions avoid the same trap. (2) An explicit architecture or approach decision was made in conversation — e.g. "we chose X over Y because...", "we decided to use X instead of Y", "the reason we're doing X is..." — save to decisions/. (3) A new project-wide convention or pattern was established during implementation — e.g. a naming rule, an API design patte
dinhanhthi/coding-friend · ★ 2 · AI & Automation · score 68

Install: claude install-skill dinhanhthi/coding-friend

# /cf-remember > **CLI Requirement:** OPTIONAL — Uses the memory MCP from `coding-friend-cli` for fast indexed search and storage. Without the CLI: falls back to grep over `docs/memory/` and direct file writes. Full functionality preserved, slower memory recall. See [CLI requirements](../../../docs/cli-requirements.md). Extract and save project knowledge. User input: **$ARGUMENTS** ## Purpose After a coding session, key knowledge gets lost — logic flows, conventions, decisions, gotchas. This skill captures that knowledge into the project's memory folder so future sessions (and humans) can quickly understand the project. ## Folder Output goes to `{docsDir}/memory/` (default: `docs/memory/`). Check `.coding-friend/config.json` for custom `docsDir` if it exists. **IMPORTANT — path resolution:** - Use `MAIN_REPO_ROOT` from the SessionStart bootstrap context (injected via session-init.sh). If absent, fall back to running `pwd` for `$CWD` and use `$CWD` as `MAIN_REPO_ROOT`. - Read config from `CF_CONFIG_FILE` (= `$MAIN_REPO_ROOT/.coding-friend/config.json`) — do NOT search sub-folders - Use `CF_DOCS_ROOT` as the docs base dir (= `$MAIN_REPO_ROOT/{docsDir}` where `docsDir` comes from config, default `docs`) - Always resolve `file_path` as an **absolute path**: `{CF_DOCS_ROOT}/memory/{category}/{name}.md` - Never use relative paths in write specs — they may resolve incorrectly when the working directory contains nested git repos ## Workflow ### Step 0: Custom Guide Run: `b