public/codex/skills/utils/memory-recall/SKILL.md
Search and recall relevant prior-session memories, earlier decisions, past debugging context, rollout notes, and durable project knowledge. Use only for questions about prior sessions or historical context, not current-code inspection.
npx skillsauth add jungho-git/jllm memory-recallInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this rule when:
Do not use memory recall for purely current-code tasks.
Memory is supporting context, not current-state proof.
When search tooling is blocked or too vague, inspect memory files directly:
${MEMSEARCH_DIR:-$HOME/.memsearch}/memory/.codex/memories/rollout_summaries/ when presentUse fs-mcp first for local file reads and searches.
Keep memory summaries short and relevant.
testing
Required phase order for non-trivial tasks: Plan, Explore, Implement, Verify, Finalize. Use for multi-step work, scoped exploration, re-planning, validation, and final synthesis.
development
Final response format: Korean-first, concise Process / Checks / Issues / Updates, optional Usage, with only actual changes, actual validation, real blockers, changed files, and measured token data when available.
development
Smallest complete change rule: preserve local code shape, extend existing patterns, avoid speculative extraction or cleanup, and include required coupled updates for correctness.
development
Code comment policy: numbered one-line `―` dividers for touched declarations and logical sections, paired outer blocks only for long regions, concise purpose comments, and no comment churn.