Document regex code navigation workflow
This commit is contained in:
@@ -66,9 +66,12 @@ cmake --build --preset windows-msvc-default --config Debug --target clean
|
||||
Codex has a repo-specific skill named `panopainter-code-navigation`. Use it when
|
||||
following C++ symbols, finding symbol families with regular expressions, tracing
|
||||
service/interface wiring, or checking platform/backend boundary usage.
|
||||
Reach for `--name-regex`, `--detail-regex`, or `--path-regex` before broad
|
||||
`rg` searches when a refactor depends on symbol identity, generated-style name
|
||||
families, signatures, or platform/backend path slices.
|
||||
For C++ refactors, use the skill before broad `rg` searches when the question
|
||||
depends on symbol identity rather than plain text. Reach for `--name-regex`,
|
||||
`--detail-regex`, or `--path-regex` when looking for generated-style name
|
||||
families, override groups, command/service families, signatures, or
|
||||
platform/backend path slices. Use normal `rg` for docs, build files, comments,
|
||||
string literals, generated command names, or exact non-C++ text.
|
||||
|
||||
Prefer compiler-aware navigation when following C++ symbols across the legacy
|
||||
flat source tree and extracted components:
|
||||
|
||||
Reference in New Issue
Block a user