메뉴
Search the codebase and Obsidian vault for relevant implementation and project context. Use when the user asks how something works, where it is implemented, or wants related notes alongside code results.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Keep an Obsidian vault project's Topics folder up to date from its Tasks (and Events), and graduate evergreen Topics into shared domain folders. Use when the user wants to refresh or maintain a project's topics, find missing or new topics, add task-to-topic backlinks, audit topic interlinking, fix orphan topics, resolve duplicate/alias collisions, convert a dated retrospective into a Task, or promote a cross-cutting Topic out of the project into a domain folder (graduation). Assumes each project under the vault has Topics/ and Tasks/ sub-folders (and usually Events/).
Resolve and operate on Channing's Obsidian vault task notes by frontmatter type. Use when the user references a task note, Jira/GitHub issue tracked by a vault task, asks to inspect or continue task context, or asks to update/capture task state. Routes task-type values such as investigation, implementation, review, experiment, and note to the appropriate specialist skill.
Read and write notes in the Obsidian vault. Use for task logs, knowledge capture, and building context.
Resolve and operate on Channing's Obsidian vault task notes by frontmatter type. Use when the user references a task note, Jira/GitHub issue tracked by a vault task, asks to inspect or continue task context, or asks to update/capture task state. Routes task-type values such as investigation, implementation, review, experiment, and note to the appropriate specialist skill.
Append a Decision Log entry, rewrite Current State, or resolve an Open Question on the active task note in Channing's vault. Use when the user says "log this decision", "update the task note", "add to the decision log", "current state has changed", "answer to the open question is X", asks for a prompt to continue the task in a new session, or otherwise asks to capture, record, or log something about the task being worked on.
Maintain a project's Research layer in an Obsidian vault — scaffold a research note from a question, spawn experiment tasks with backlinks, roll experiment findings up into the research note, sync open questions, and on conclusion graduate durable findings into Topics. Use when the user wants to start a piece of research, add an experiment to a research question, update a research note from its experiments, review open questions, or conclude a research question. Sibling of obsidian-topic-maintainer; assumes projects under the vault have Research/, Tasks/, Topics/ (and usually Events/) sub-folders.
| name | code-query |
| description | Search the codebase and Obsidian vault for relevant implementation and project context. Use when the user asks how something works, where it is implemented, or wants related notes alongside code results. |
Search codebase and vault documents for relevant information.
/code-query <search-term>
Where $ARGUMENTS is the search term or question to investigate.
vault skill.codegraph/ exists use the CodeGraph routing below; otherwise search files using Grep/GlobWhen .codegraph/ exists, route by question shape:
| Question | Tool |
|---|---|
| "Where is X defined?" / "Find symbol named X" | codegraph_search |
| "What calls function Y?" | codegraph_callers |
| "What does Y call?" | codegraph_callees |
| "How does X reach/become Y? / trace the flow" | codegraph_trace (one call = the whole path, incl. callback/React/JSX dynamic hops) |
| "What would break if I changed Z?" | codegraph_impact |
| "Show me Y's signature / source / docstring" | codegraph_node |
| "Give me focused context for a task/area" | codegraph_context |
| "See several related symbols' source at once" | codegraph_explore |
| "What files exist under path/" | codegraph_files |
| "Is the index healthy?" | codegraph_status |
Rules of thumb:
codegraph_context first, then ONE codegraph_explore for the source it surfaces. For flows, codegraph_trace from→to returns the whole path in one call — don't rebuild it with codegraph_search + codegraph_callers. CodeGraph IS the pre-built index; grep+read loops repeat its work at higher cost.rg's surfaces).codegraph_search returns kind + location + signature in one call.codegraph_context is one call) and don't loop codegraph_node over many symbols (one codegraph_explore is cheaper).rg pass when the term also appears as text or results look sparse.codegraph init -i; if declined, locate-then-read with rg./code-query authentication flow
/code-query how errors are handled
/code-query database connection