Skip to main content

sift-memory

Use this skill when an agent needs local historical context from AI coding assistant sessions, prior project conversations, debugging history, implementation decisions, or user asks to search Claude Code, Codex, or Cursor chat history. It teaches agents to use the local-only `sift` CLI for indexed full-text search across Claude Code, Codex, and Cursor logs without network calls.

소스 정보

저장소
sahit-sai/saviaa
최근 소스 활동
2026년 7월 18일 11:03
감지된 SKILL.md 언어
영어
스타
0
포크
0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
2 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
sift-memory
description
Use this skill when an agent needs local historical context from AI coding assistant sessions, prior project conversations, debugging history, implementation decisions, or user asks to search Claude Code, Codex, or Cursor chat history. It teaches agents to use the local-only `sift` CLI for indexed full-text search across Claude Code, Codex, and Cursor logs without network calls.
compatibility
Agent Skills-compatible clients including Codex, Claude Code, Cursor-compatible agents, and VS Code/GitHub Copilot agent mode. Requires Node.js 20+ and the local `sift` CLI or this repo's `node ./bin/sift.js`.
# Sift Memory Use `sift` as a local memory search layer for prior AI coding-assistant sessions. It reads only local Claude Code, Codex, and Cursor logs/databases and writes only its own index under `~/.sift/`. ## Command Resolution Prefer the installed CLI: ```sh sift --help ``` When working inside the `sift` repository and the global command is unavailable, use: ```sh node ./bin/sift.js --help ``` Do not use `npx` or any network-based install path. If neither command works, tell the user to install `sift` locally. ## Actions ### sift_index Refresh the local index before memory-heavy work, after new logs were created, or when search says no index exists: ```sh sift index ``` Use the repo-local fallback when needed: ```sh node ./bin/sift.js index ``` Use a full rebuild only when the user asks, parser/index behavior changed, or results look stale after an incremental run: ```sh sift index --full ``` ### sift_search Search prior local sessions with targeted queries: ```sh sift "<query>" --limit 10 ``` Filter by source when useful: ```sh sift "<query>" --tool codex --limit 10 sift "<query>" --tool claude --limit 10 sift "<query>" --tool cursor --limit 10 ``` Good queries are concrete: project names, command names, file names, bug symptoms, package names, decisions, or user phrasing. Prefer a few focused searches over one broad search. ### sift_list List recent indexed sessions when you need orientation before choosing search terms: ```sh sift list --limit 10 ``` Filter by source when useful: ```sh sift list --tool codex --limit 10 ``` ## Workflow 1. Use this skill when local session memory could materially improve the answer. 2. Run `sift index` unless the task is tiny or the index is known to be fresh. 3. Run `sift_search` with 1-3 focused queries. 4. Use the results as private local context. Summarize only the relevant facts needed for the task. 5. Do not paste large raw logs. Do not expose secrets, credentials, tokens, private personal data, or unrelated session contents. ## Privacy Keep the workflow local and read-only for source logs: - Do not send `sift` results to remote services. - Do not add telemetry, sync, embeddings, or network calls. - Do not write to Claude Code, Codex, or Cursor source logs/databases. - Treat `~/.sift/index.json` as local private context.
GitHub에서 보기