@handsupmin/gc-tree 0.7.16 → 0.7.18
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 +10 -0
- package/package.json +1 -1
package/dist/src/scaffold.js
CHANGED
|
@@ -8,6 +8,11 @@ function renderCodexAgentsSnippet() {
|
|
|
8
8
|
'',
|
|
9
9
|
'- Treat the active gctree branch as a **gc-branch** when you describe it to users.',
|
|
10
10
|
'- gctree init installs SessionStart and UserPromptSubmit hooks that auto-check gc-tree before work.',
|
|
11
|
+
'- When you encounter an unfamiliar term, acronym, concept, or domain word, follow this protocol **before** grepping or reading code files:',
|
|
12
|
+
' 1. Run `gctree resolve --query "<term>"` — if matched, use the result directly.',
|
|
13
|
+
' 2. If no match, try broader related queries to check if the concept lives in any doc.',
|
|
14
|
+
' 3. If the concept exists in a doc but was not indexed → propose adding it as an Index Entry to that doc (so future resolves find it).',
|
|
15
|
+
' 4. If it does not exist anywhere → decide whether a new doc is needed and propose it to the user.',
|
|
11
16
|
'- When a UserPromptSubmit hook provides `[gc-tree] PRE-TASK CONTEXT`, treat it as mandatory pre-reading before any tool use.',
|
|
12
17
|
'- If the injected summaries contain enough information to answer the question or complete the task, respond directly from them **without calling any tools**. Do not grep, explore, or read code files to confirm what the summaries already cover.',
|
|
13
18
|
'- Only use tools if the summaries are clearly insufficient — meaning the answer cannot be derived from them at all.',
|
|
@@ -113,6 +118,11 @@ function renderClaudeSnippet() {
|
|
|
113
118
|
'',
|
|
114
119
|
'- Treat the active gctree branch as a **gc-branch** in user-facing language.',
|
|
115
120
|
'- gctree init installs SessionStart and UserPromptSubmit hooks that auto-inject gc-tree context before every prompt.',
|
|
121
|
+
'- When you encounter an unfamiliar term, acronym, concept, or domain word, follow this protocol **before** grepping or reading code files:',
|
|
122
|
+
' 1. Run `gctree resolve --query "<term>"` — if matched, use the result directly.',
|
|
123
|
+
' 2. If no match, try broader related queries to check if the concept lives in any doc.',
|
|
124
|
+
' 3. If the concept exists in a doc but was not indexed → propose adding it as an Index Entry to that doc (so future resolves find it).',
|
|
125
|
+
' 4. If it does not exist anywhere → decide whether a new doc is needed and propose it to the user.',
|
|
116
126
|
'- When a UserPromptSubmit hook provides `[gc-tree] PRE-TASK CONTEXT`, treat it as mandatory pre-reading before any tool use.',
|
|
117
127
|
'- If the injected summaries contain enough information to answer the question or complete the task, respond directly from them **without calling any tools**. Do not grep, explore, or read code files to confirm what the summaries already cover.',
|
|
118
128
|
'- Only use tools if the summaries are clearly insufficient — meaning the answer cannot be derived from them at all.',
|