@handsupmin/gc-tree 0.7.15 → 0.7.16

package/dist/src/hook.js

@@ -55,9 +55,9 @@ function buildMatchContext({ gcBranch, currentRepo, repoScopeStatus, query, matc
     return [
         `[gc-tree] PRE-TASK CONTEXT — read before any tool use or code exploration.`,
         `gc-branch: "${gcBranch}" | repo: "${currentRepo || 'unscoped'}" (scope: ${repoScopeStatus}) | query: "${query}".`,
-        `Do NOT call Explore, grep, or read code files until you have read and internalized these summaries:`,
+        `If these 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 to confirm what the summaries already cover. Only use tools if the summaries are clearly insufficient.`,
         formatMatches(matches),
-        `Read full docs (gctree resolve --id <id>) only if summaries are insufficient. Each doc has a ## Summary section — read that first.`,
+        `Read full docs (gctree resolve --id <id>) only if summaries are clearly insufficient — meaning the answer cannot be derived from them at all.`,
     ].join('\n');
 }
 function buildSelfReviewAppend(promptCount) {
@@ -65,7 +65,7 @@ function buildSelfReviewAppend(promptCount) {
         `\n[gc-tree] CONTEXT SELF-REVIEW (every ${SELF_REVIEW_INTERVAL} prompts — this is prompt #${promptCount}):`,
         `At the END of your response to this task, review the current gc-tree global context and compare it against what you have observed or changed in this session.`,
         `If any docs need updating (new conventions discovered, corrected info, new repos or workflows, outdated content), propose the specific changes to the user and ask whether to apply them.`,
-        `Use \`/gc-update-global-context\` (Claude Code) or \`gctree update-global-context\` (CLI) to apply.`,
+        `Use \`/gc-update-global-context\` (Claude Code), \`$gc-update-global-context\` (Codex), or \`gctree update-global-context\` (CLI) to apply.`,
         `If nothing meaningful changed, skip silently — do not mention this review to the user.`,
     ].join('\n');
 }

package/dist/src/scaffold.js

@@ -8,7 +8,10 @@ function renderCodexAgentsSnippet() {
         '',
         '- Treat the active gctree branch as a **gc-branch** when you describe it to users.',
         '- gctree init installs SessionStart and UserPromptSubmit hooks that auto-check gc-tree before work.',
-        '- Use the hook-injected gc-tree context first. If hooks are unavailable or clearly stale, run `gctree status` and `gctree resolve --query "<task>"` yourself before planning or implementation.',
+        '- When a UserPromptSubmit hook provides `[gc-tree] PRE-TASK CONTEXT`, treat it as mandatory pre-reading before any tool use.',
+        '- 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.',
+        '- Only use tools if the summaries are clearly insufficient — meaning the answer cannot be derived from them at all.',
+        '- If hooks are unavailable or clearly stale, run `gctree status` and `gctree resolve --query "<task>"` yourself before planning or implementation.',
         '- Use `$gc-onboard` only for an empty gc-branch.',
         '- Use `$gc-update-global-context` when durable context in the active gc-branch should change.',
         '',
@@ -19,8 +22,9 @@ function renderCodexBootstrapPrompt() {
         '# gctree Bootstrap',
         '',
         '- Keep the active gc-branch explicit whenever global context matters.',
-        '- Trust auto-resolved gc-tree hook context first; if it is missing, resolve reusable global context before planning or implementation.',
-        '- Read summaries first and only open full docs when needed.',
+        '- When hook-injected PRE-TASK CONTEXT is present, read it first. If summaries already answer the question, respond directly without any tool calls.',
+        '- Only use tools (grep, file read, explore) if summaries are clearly insufficient — meaning the answer cannot be derived from them at all.',
+        '- If hook context is missing, resolve reusable global context before planning or implementation.',
         '- Treat gctree docs as explicit source-of-truth markdown, not hidden memory.',
         '',
     ].join('\n');
@@ -109,7 +113,9 @@ function renderClaudeSnippet() {
         '',
         '- Treat the active gctree branch as a **gc-branch** in user-facing language.',
         '- gctree init installs SessionStart and UserPromptSubmit hooks that auto-inject gc-tree context before every prompt.',
-        '- When a UserPromptSubmit hook provides `[gc-tree] PRE-TASK CONTEXT`, treat it as mandatory pre-reading. Read and internalize the injected summaries **before** calling any tools (Explore, grep, Read, Bash). Do not explore code first.',
+        '- When a UserPromptSubmit hook provides `[gc-tree] PRE-TASK CONTEXT`, treat it as mandatory pre-reading before any tool use.',
+        '- 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.',
+        '- Only use tools if the summaries are clearly insufficient — meaning the answer cannot be derived from them at all.',
         '- If hooks are unavailable or clearly stale, run `gctree status` and `gctree resolve --query "<task>"` yourself before planning or implementation.',
         '- Use `/gc-onboard` only for an empty gc-branch.',
         '- Use `/gc-update-global-context` when durable context in the active gc-branch should change.',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@handsupmin/gc-tree",
-  "version": "0.7.15",
+  "version": "0.7.16",
   "description": "Global Context Tree, a lightweight branch-aware global context orchestrator for AI coding tools",
   "type": "module",
   "private": false,