メニュー
CodeGraph MCP server setup — install, index, and configure semantic code search. Use when setting up CodeGraph in a new repo, re-indexing, or troubleshooting codegraph MCP.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | codegraph-setup |
| description | CodeGraph MCP server setup — install, index, and configure semantic code search. Use when setting up CodeGraph in a new repo, re-indexing, or troubleshooting codegraph MCP. |
Check whether CodeGraph is installed with command -v codegraph. In this managed OpenCode setup, install or repair it through bootstrap.sh; do not run codegraph install, because opencode.json already owns the MCP configuration. On an unmanaged machine, follow the official installer.
Initialize the current project:
codegraph init
CodeGraph is configured as an MCP server in opencode.json:
"codegraph": {
"type": "local",
"command": ["codegraph", "serve", "--mcp"]
}
On macOS with Homebrew: /opt/homebrew/bin/codegraph serve --mcp
codegraph sync only when the watcher is disabled or a script needs an explicit incremental update.codegraph_explore for the project..codegraph/ directory, the MCP server exposes no tools.Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Review upstream changes to the local my-opencode reviewer swarm before selectively applying them. Use whenever the user asks to pull, sync, inspect, compare, or adopt reviewer or swarm changes from ~/Documents/yo/my-opencode. Never use it to install the upstream configuration wholesale.
Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", and whenever they complain about over-engineering, bloat, boilerplate, or unnecessary dependencies.
Use whenever the task involves writing, drafting, revising, or reviewing a system prompt for an AI agent — autonomous or semi-autonomous LLM systems that use tools in a loop, including operator agents, research/sub-agents, tool-using assistants, MCP servers, multi-agent orchestrators, and coding agents. Trigger even when the user says "instructions", "system message", "agent persona", or "rules for the model", not just the word "prompt". Do NOT use for one-shot prompts (classification, single generation, single Q&A) — those need lighter prompt techniques, not the full agent skeleton.