@handsupmin/gc-tree 0.8.7 → 0.8.8
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 +8 -6
- package/package.json +1 -1
package/dist/src/scaffold.js
CHANGED
|
@@ -8,8 +8,9 @@ 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
|
-
'-
|
|
12
|
-
'
|
|
11
|
+
'- Before starting ANY codebase task — new feature, schema change, bug fix, admin work, or any question about how something works — run `gctree resolve` first. Do not assume you know the domain from code alone. Field names, model names, repo names, and feature names are NOT self-explanatory; always verify workflows and cross-repo relationships via gc-tree before touching code.',
|
|
12
|
+
'- Follow this scope-aware protocol before any grep, file read, or code exploration:',
|
|
13
|
+
' 1. Always run `gctree resolve --query "<task or term>"` first. If matched, use the result directly.',
|
|
13
14
|
' 2. Only if the current repo scope is **included** (not unmapped/excluded): if step 1 found nothing, try broader related queries to check if the concept exists in any doc.',
|
|
14
15
|
' 3. If the concept exists in a doc but was not indexed → propose adding it as an Index Entry to that doc.',
|
|
15
16
|
' 4. If it does not exist anywhere → decide whether a new doc is needed and propose it to the user.',
|
|
@@ -28,8 +29,8 @@ function renderCodexBootstrapPrompt() {
|
|
|
28
29
|
'# gctree Bootstrap',
|
|
29
30
|
'',
|
|
30
31
|
'- Keep the active gc-branch explicit whenever global context matters.',
|
|
31
|
-
'-
|
|
32
|
-
' 1. Run `gctree resolve --query "<term>"`.',
|
|
32
|
+
'- Before any codebase task — feature, schema change, bug fix, admin work — do **not** grep or read code first. Follow this exact order:',
|
|
33
|
+
' 1. Run `gctree resolve --query "<task or term>"`.',
|
|
33
34
|
' 2. If that misses, run broader related `gctree resolve` queries.',
|
|
34
35
|
' 3. If the concept is documented but not indexed, propose adding it as an Index Entry to the right doc.',
|
|
35
36
|
' 4. Only if gc-tree still does not answer it should you search code or repo docs.',
|
|
@@ -124,8 +125,9 @@ function renderClaudeSnippet() {
|
|
|
124
125
|
'',
|
|
125
126
|
'- Treat the active gctree branch as a **gc-branch** in user-facing language.',
|
|
126
127
|
'- gctree init installs SessionStart and UserPromptSubmit hooks that auto-inject gc-tree context before every prompt.',
|
|
127
|
-
'-
|
|
128
|
-
'
|
|
128
|
+
'- Before starting ANY codebase task — new feature, schema change, bug fix, admin work, or any question about how something works — run `gctree resolve` first. Do not assume you know the domain from code alone. Field names, model names, repo names, and feature names are NOT self-explanatory; always verify workflows and cross-repo relationships via gc-tree before touching code.',
|
|
129
|
+
'- Follow this scope-aware protocol before any grep, file read, or code exploration:',
|
|
130
|
+
' 1. Always run `gctree resolve --query "<task or term>"` first. If matched, use the result directly.',
|
|
129
131
|
' 2. Only if the current repo scope is **included** (not unmapped/excluded): if step 1 found nothing, try broader related queries to check if the concept exists in any doc.',
|
|
130
132
|
' 3. If the concept exists in a doc but was not indexed → propose adding it as an Index Entry to that doc.',
|
|
131
133
|
' 4. If it does not exist anywhere → decide whether a new doc is needed and propose it to the user.',
|