recall

Files (1)

• SKILL.md

SKILL.md (first lines)

# Recall Skill — 과거 컨텍스트 회상

## When to Activate
You should proactively activate this skill when the user asks questions that imply they need
historical context about the project — past decisions, previous implementations, resolved issues,
or any knowledge that should exist in the team's Obsidian vault.

## Activation Steps

Optional Jev reranking runs only with separately approved project/vault consent.
Never enable it just to answer a search. Check `reranking.provider` in helper
output; failure preserves local results. Use the `jev` skill for setup and never
collect keys in chat or tool input.

1. **Check Environment**
   Verify `$OBSIDIAN_VAULT` is set and the directory exists.
   If not set, inform the user and suggest running `/oh-my-obsidian:setup`.

2. **Search Strategy**
   - **MCP Semantic Search** (optional): If the user has already configured an MCP server with
     recall/search capability, use it first. Do not install, start, or require an MCP server.
   - **Local Search** (default): Otherwise run the bundled keyword-search helper:
     ```
     node "$CLAUDE_PLUGIN_ROOT/plugins/oh-my-obsidian/scripts/vault-ops.mjs" recall --query "<query>"
     ```
     The helper walks local Markdown files and supplements those results with matching
     `session-catalog.json` metadata when available.
   - **Type-Aware Search**: If the query includes a type hint (e.g., '이전 결정', 'past decision',
     '트러블슈팅'), use grep pattern `type:decision` or `type:troubleshooting` for more precise matching.
     Type mapping: 세션기록→session-log, 의사결정→decision, 트러블슈팅→troubleshooting, 회의록→meeting-notes
     Search across both layers:
     - 서비스 레이어: all project-specific knowledge folders
     - 작업기록 레이어: 세션기록, 의사결정, 트러블슈팅, 회의록

3. **Result Processing**
   - Read matching files
   - Extract relevant sections
   - Prioritize recent documents
   - Group by category
   - Present concisely — only return what's relevant to the current question

4. **Output Format**
   ```
   📋 회상 결과

   [의사결정] YYYY-MM-DD — 제목 (type: decision)
   > 관련 내용 발췌...

   [트러블슈팅] YYYY-MM-DD — 제목 (type: troubleshooting)
   > 관련 내용 발췌...
   ```

5. **Integration**
   After presenting recalled context, proactively connect it to the user's current question.
   "이전에 X라고 결정했는데, 현재 상황에서도 동일하게 적용할까요?"

From hongdangmoo49/oh-my-obsidian, MIT.

More from hongdangmoo49/oh-my-obsidian