docs(agents): say when ccc comes before grep
Co-Authored-By: Claude Mythos 5.1 <noreply@anthropic.com>
This commit is contained in:
parent
4940a7066d
commit
f5878f1f06
1 changed files with 7 additions and 6 deletions
|
|
@ -133,12 +133,13 @@ on your own. Command forms, flags, dataset sharing and failure modes are in the
|
||||||
checkout stays first choice when it exists. Never call
|
checkout stays first choice when it exists. Never call
|
||||||
`ask_codebase` on your own — it spawns a nested server-side agent
|
`ask_codebase` on your own — it spawns a nested server-side agent
|
||||||
(minutes per call, shared vLLM); use it only when explicitly asked.
|
(minutes per call, shared vLLM); use it only when explicitly asked.
|
||||||
- **`ccc` for semantic code search.** Repos containing a `.cocoindex_code/`
|
- **`ccc` before `grep` for concept questions.** In a repo with a
|
||||||
directory are indexed by `ccc`. Reach for it on conceptual questions ("where
|
`.cocoindex_code/` directory, a question about a concept ("where is X
|
||||||
is X used / what handles Z"), where a keyword grep would miss indirect usage:
|
handled", "what talks to Y", "which code does Z") starts with
|
||||||
`ccc search '<concept>'` from the project root. It is embeddings only: exact
|
`ccc search '<concept>'` from the project root, then `grep` verifies what it
|
||||||
strings (UUIDs, ticket IDs, error messages) stay with `grep`/`rg`. Details and
|
found. An exact string (UUID, ticket ID, error message, identifier) goes
|
||||||
gotchas in the `ccc` skill.
|
straight to `grep`/`rg`: ccc is embeddings only and will not find it. Gotchas
|
||||||
|
in the `ccc` skill.
|
||||||
- **`ccc index` / `ccc init` are read-safe maintenance.** They only write to the
|
- **`ccc index` / `ccc init` are read-safe maintenance.** They only write to the
|
||||||
gitignored `.cocoindex_code/` directory, never to source. Run them without
|
gitignored `.cocoindex_code/` directory, never to source. Run them without
|
||||||
confirmation prompts; treat like `grep` for permission purposes.
|
confirmation prompts; treat like `grep` for permission purposes.
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue