Document regex code navigation rule
This commit is contained in:
@@ -320,7 +320,10 @@ XML; full document/app integration is debt-tracked as DEBT-0010 and full PPI
|
||||
body parsing is debt-tracked as DEBT-0013. Agent code navigation now includes
|
||||
`scripts/dev/clangd_nav.py` with symbol/detail/path regex filters and a
|
||||
`panopainter_clangd_nav_regex_self_test` CTest so broad symbol-family searches
|
||||
can be validated before they guide refactors.
|
||||
can be validated before they guide refactors. Agents must use the
|
||||
`panopainter-code-navigation` skill before broad text search whenever C++
|
||||
symbol identity, generated-style symbol families, declarations/definitions,
|
||||
override groups, or platform/backend path slices are the real question.
|
||||
|
||||
Implementation tasks:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user