القائمة
Isolated codebase exploration that preserves your main context. Use when you need to understand code structure, trace call paths, or gather evidence before making changes. Spawns an explorer subagent.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Build the project and verify it compiles cleanly. Use after making changes to confirm nothing is broken before running tests. Reads the build command from context/build.md.
Auto-configure .github/copilot-instructions.md and context/ knowledge docs for a new project. Use when setting up Brain Bootstrap in a new repository. Discovers the codebase, fills in templates, and writes project-specific configuration.
Save session state before context gets full or before ending. Writes current task state, branch, and loaded docs to context/tasks/todo.md so the next session can resume cleanly.
Clean workspace — build artifacts, dependencies, caches, Docker volumes, or temp files. Accepts arguments like build, deps, all, cache, docker, tasks, reinstall.
Load all relevant context/ knowledge files for a domain area. Use at session start or when switching to a new topic. Accepts a domain keyword like api, database, auth, build, security.
Query the database — list schemas, tables, describe a table, or run SQL. Accepts arguments like schemas, tables, describe <table>, or raw SQL.
| name | research |
| description | Isolated codebase exploration that preserves your main context. Use when you need to understand code structure, trace call paths, or gather evidence before making changes. Spawns an explorer subagent. |
Explore the codebase without polluting your main context.
"Spawn an explorer subagent to [describe the research goal]. Return a structured summary with: files examined, relevant symbols, call path trace, and key findings."
The explorer runs in read-only mode in isolated context — your main thread stays clean.
find . -name '*.ts' -path '*/auth/*' | head -20
grep -rn --color=never 'functionName' --include='*.ts' . | head -30
# 1. Find where the function is defined
grep -rn --color=never 'def functionName\|function functionName\|functionName =' . | head -10
# 2. Find all callers
grep -rn --color=never 'functionName(' . | grep -v 'def functionName\|function functionName' | head -20
Use file reading tools — do NOT cat the whole file.
After research, summarize findings:
## Research Summary: <topic>
### Files examined
- path/to/file.ts — reason
### Key symbols found
- SymbolName (file:line) — what it does
### Call path trace
Entry → ServiceA.method → ServiceB.method → DB query
### Key findings
1. Finding 1
2. Finding 2
### Open questions
- ?
context/tasks/research-notes.md (not in main context)