use-cli-recall
Search past Claude Code/Codex sessions via recall CLI.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Search past Claude Code/Codex sessions via recall CLI.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
issue が build に投入できる形かを検分し、verdict (build-ready / needs-plan / needs-fix) と指摘を返す。起票には使わない (/issue)。PR のスクリーニングには使わない (/preview)。
Inspect whether an issue is in shape to hand to build, returning a verdict (build-ready / needs-plan / needs-fix) and the findings. Do NOT use to file an issue (use /issue) or to screen a PR (use /preview).
critic-design による敵対的批判を伴う設計探索。生き残った案を構造化 plan にまとめ、自己点検して呼び出し元に返す。plan の永続先は issue の Plan 節が唯一。計画意図のないコードベース調査には使わない (代わりに /research)。
Design exploration with adversarial critique by critic-design. Assembles the surviving approach into a structured plan, self-checks it, and returns it to the caller. The issue's Plan section is the plan's only persistent home. Do NOT use for codebase investigation without planning intent (use /research instead).
構造化されたタイトルと本文で GitHub Issue を生成する。単独で成立し、前段を要求しない。challenge / research の成果物が会話にあれば本文の根拠に使い、/think の plan 下書きがあれば `## Plan` 節へ移設する。issue 番号を渡すと、起票済みで Plan 節を持たない issue へ plan を転記する。
Generate GitHub Issue with structured title and body. Standalone; requires no upstream stage. When challenge / research artifacts exist in the conversation, they feed the body's evidence; when a /think plan draft exists, it is transferred into the `## Plan` section. Given an issue number, it transfers a plan into a filed issue that has no Plan section.
| name | use-cli-recall |
| description | Search past Claude Code/Codex sessions via recall CLI. |
| when_to_use | 前に, あの時, また同じ, あの件, past decisions, recurring mistake, module first contact, temporal reference, structural echo, vague back-reference |
| allowed-tools | Bash Read |
| user-invocable | false |
When one applies, call without deliberation.
| Trigger | Signal |
|---|---|
| Temporal reference | 「前に」「あの時」 past events / decisions |
| Structural echo | Current problem mirrors a past situation |
| Repetition | 「また同じ」 recurring mistake |
| Vague back-reference | 「あの件」 past work without specifics |
| Module first contact | First edit to a file/module this session |
| Purpose | Command |
|---|---|
| Search | recall search "query". Shorthand: recall "query" |
| Last N days | recall search "query" --days N |
| Project filter | recall search "query" --project <path> |
| Source filter | recall search "query" --source claude or --source codex |
| Limit results | recall search "query" --limit N. Default 10, max 100 |
| Show session | recall show <session-id> |
| Status | recall status |
| Incremental index | recall index |
| Full rebuild | recall index --force |
Write bilingual queries upfront (e.g. recall "認証 auth"). FTS5 trigram tokenization cannot match JA terms of 2 chars or fewer; 認証 and 依存 hit 0. Embeddings do not bridge EN⇄JA (thkt/recall#51). Including both languages covers each search path.
recall does not expand queries (caller-is-LLM, thkt/recall#25). Hybrid search returns nearest neighbors, so a poor query yields low-relevance results rather than 0 hits. When results are empty or low-relevance, rewrite the query yourself and retry once: synonyms, EN⇄JA variants, related concept terms.
use-cli-recall answers past decisions; ugrep / bfs answer the current code state. Run both on these triggers.
| Trigger | recall query | code search |
|---|---|---|
| Module first contact | module name, design rationale | module name, key identifiers |
| Structural echo | past similar problem | current similar code |