@handsupmin/gc-tree 0.8.0 → 0.8.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/src/scaffold.js +5 -0
- package/package.json +1 -1
package/dist/src/scaffold.js
CHANGED
|
@@ -27,6 +27,11 @@ function renderCodexBootstrapPrompt() {
|
|
|
27
27
|
'# gctree Bootstrap',
|
|
28
28
|
'',
|
|
29
29
|
'- Keep the active gc-branch explicit whenever global context matters.',
|
|
30
|
+
'- If you encounter an unfamiliar term, acronym, concept, domain word, or internal name, do **not** grep or read code first. Follow this exact order:',
|
|
31
|
+
' 1. Run `gctree resolve --query "<term>"`.',
|
|
32
|
+
' 2. If that misses, run broader related `gctree resolve` queries.',
|
|
33
|
+
' 3. If the concept is documented but not indexed, propose adding it as an Index Entry to the right doc.',
|
|
34
|
+
' 4. Only if gc-tree still does not answer it should you search code or repo docs.',
|
|
30
35
|
'- When hook-injected PRE-TASK CONTEXT is present, read it first. If summaries already answer the question, respond directly without any tool calls.',
|
|
31
36
|
'- Only use tools (grep, file read, explore) if summaries are clearly insufficient — meaning the answer cannot be derived from them at all.',
|
|
32
37
|
'- If hook context is missing, resolve reusable global context before planning or implementation.',
|