@handsupmin/gc-tree 0.8.11 → 0.8.13

package/dist/src/hook.js

@@ -27,9 +27,13 @@ function limitMatches(matches, max = 3) {
 function formatMatches(matches) {
     return limitMatches(matches)
         .map((match, index) => {
-        const summary = match.summary?.trim();
-        return summary
-            ? `${index + 1}. ${match.title} [${match.id}]\n   > ${summary}`
+        const summary = match.summary?.trim() ?? '';
+        const excerpt = match.excerpt?.trim() ?? '';
+        // Use summary if it looks actionable (long enough to contain patterns).
+        // Fall back to a trimmed excerpt when summary is a short description-only sentence.
+        const context = summary.length >= 60 ? summary : (excerpt.slice(0, 300) || summary);
+        return context
+            ? `${index + 1}. ${match.title} [${match.id}]\n   > ${context}`
             : `${index + 1}. ${match.title} [${match.id}]`;
     })
         .join('\n');

package/dist/src/onboarding-protocol.js

@@ -36,7 +36,7 @@ export function onboardingProtocolLines() {
         'Treat `index.md` as concept-first: show the keywords a user or AI would search for, not just broad document titles.',
         'Generate index entries automatically from primary concept names, aliases, repository nicknames, and workflow labels when those are clear.',
         'Split glossary docs when a concept is likely to be searched directly, needs more than a short definition, or carries workflow/constraint details; keep only low-value leftover terms in a shared glossary.',
-        'Keep each doc summary-first so the top section gives the gist before deeper details.',
+        'The `## Summary` section of every doc must be actionable, not descriptive — write the actual patterns, commands, or constraints a developer needs, not a sentence about what the doc covers. Bad: "이 문서는 updateCollection 패턴을 설명합니다." Good: "updateCollection: { ...dto } spread 필수. return plainToInstance(Res, result satisfies Res). 새 필드 추가 = DTO → 서비스 → 컨트롤러 순서." The summary is injected into the AI context before every task — if it reads like a table of contents entry, it is useless.',
         'Treat `index.md` as a human-readable dictionary-style table of contents grouped by category headings and `label -> path` entries.',
     ];
 }

package/dist/src/update.js

@@ -52,7 +52,7 @@ export async function selfUpdate(home) {
     }
     process.stderr.write('\nUpdating gctree to latest...\n');
     try {
-        execSync('npm install -g @handsupmin/gc-tree', { stdio: 'inherit' });
+        execSync('npm install -g @handsupmin/gc-tree --force', { stdio: 'inherit' });
     }
     catch {
         process.stderr.write('\nnpm registry may not have propagated the latest version yet. Wait a minute and retry: gctree update\n');

package/package.json

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

package/skills/onboard/SKILL.md

@@ -39,7 +39,7 @@ Use this when a user wants to create global context for a product, company, or w
 - when the inspected evidence already covers a repository well enough, ask only for missing deltas instead of re-asking role, paths, and workflow from scratch
 - only ask open-ended repository questions when the needed detail cannot be recovered responsibly from local evidence
 - ask about glossary terms and default verification commands before you finish
-- write compact source docs with a required `## Summary` section near the top
+- write compact source docs with a required `## Summary` section near the top; the `## Summary` must be actionable — write the actual patterns, commands, or constraints a developer needs, not a sentence about what the doc covers (bad: "이 문서는 X를 설명합니다"; good: "updateX: { ...dto } spread 필수. return plainToInstance(Res, result satisfies Res). 새 필드 추가 = DTO → 서비스 → 컨트롤러 순서."); the summary is injected into AI context before every task — if it reads like a table of contents entry, it is useless
 - prefer an encyclopedia-style context set with many small docs instead of a few broad docs
 - prefer category directories like `docs/role/`, `docs/repos/`, `docs/domain/`, `docs/workflows/`, `docs/conventions/`, and `docs/infra/`
 - prefer one concept, one repository, one workflow, or one convention per file when possible