@basestream/cli 0.2.1 → 0.2.2

package/dist/cli.mjs

@@ -921,6 +921,12 @@ async function login() {
 var CLAUDE_DIR = path2.join(os2.homedir(), ".claude");
 var CLAUDE_SETTINGS_PATH = path2.join(CLAUDE_DIR, "settings.json");
 var CLAUDE_SKILLS_PATH = path2.join(CLAUDE_DIR, "skills", "bs-summarize.md");
+var CLAUDE_MD_PATH = path2.join(CLAUDE_DIR, "CLAUDE.md");
+var CLAUDE_MD_MARKER = "<!-- basestream -->";
+var CLAUDE_MD_RULE = `${CLAUDE_MD_MARKER}
+- Before starting any non-trivial task, if the reason or context behind the work isn't already clear, ask: "What's the context for this?" Skip this for small tasks, typo fixes, or anything self-explanatory.
+- After completing any meaningful work (fixing a bug, implementing a feature, making a significant change), invoke /bs-summarize to keep the session summary up to date. Include the "why" if it was provided.
+<!-- /basestream -->`;
 var HOOK_COMMAND = "npx @basestream/cli _hook-stop";
 var HOOK_MARKER = "_hook-stop";
 var SKILL_CONTENT = `---
@@ -928,15 +934,39 @@ name: bs-summarize
 description: Update the Basestream session summary with what's been accomplished so far
 ---
 
-Write a concise summary of what has been accomplished in this coding session so far. Focus on:
+First, read the existing summary file at \`~/.basestream/sessions/\${CLAUDE_SESSION_ID}-summary.md\` if it exists \u2014 this is the running record of work done so far this session.
+
+Then write an updated summary that aggregates the previous summary with everything that has happened since. Focus on:
+- Why the work was done (if context was provided \u2014 skip if not known)
 - What was built, fixed, or changed (be specific about features/bugs)
 - Which parts of the codebase were touched
 - Any key decisions made
 
-Keep it to 2-4 sentences, plain prose, no bullet points.
+Do not just append \u2014 synthesize everything into a single cohesive summary. Merge related work together, avoid repeating the same point twice, and drop anything superseded by later changes. Be concise \u2014 let the scope of the work determine the length. A small fix deserves one sentence; a large multi-part session can be a short paragraph. Plain prose, no bullet points.
+
+Write the result to \`~/.basestream/sessions/\${CLAUDE_SESSION_ID}-summary.md\`, overwriting the file.
+`;
+function injectClaudeMdRule() {
+  let existing = "";
+  if (fs2.existsSync(CLAUDE_MD_PATH)) {
+    existing = fs2.readFileSync(CLAUDE_MD_PATH, "utf-8");
+  }
+  let updated;
+  if (existing.includes(CLAUDE_MD_MARKER)) {
+    updated = existing.replace(/<!-- basestream -->[\s\S]*?<!-- \/basestream -->/, CLAUDE_MD_RULE);
+    fs2.writeFileSync(CLAUDE_MD_PATH, updated);
+    check("Updated Basestream rules in ~/.claude/CLAUDE.md");
+  } else {
+    updated = existing ? `${existing.trimEnd()}
 
-Write the summary to the file \`~/.basestream/sessions/\${CLAUDE_SESSION_ID}-summary.md\` \u2014 overwrite if it exists.
+${CLAUDE_MD_RULE}
+` : `${CLAUDE_MD_RULE}
 `;
+    fs2.mkdirSync(CLAUDE_DIR, { recursive: true });
+    fs2.writeFileSync(CLAUDE_MD_PATH, updated);
+    check("Injected Basestream rules into ~/.claude/CLAUDE.md");
+  }
+}
 function installSkill() {
   const skillsDir = path2.dirname(CLAUDE_SKILLS_PATH);
   fs2.mkdirSync(skillsDir, { recursive: true });
@@ -1009,6 +1039,7 @@ async function init() {
   console.log();
   injectClaudeCodeHook();
   installSkill();
+  injectClaudeMdRule();
   ensureDirs();
   check(`Created ~/.basestream/buffer/`);
   console.log();
@@ -4481,7 +4512,7 @@ async function main() {
     process.exit(0);
   }
   if (command === "--version" || command === "-v") {
-    console.log(true ? "0.2.1" : "dev");
+    console.log(true ? "0.2.2" : "dev");
     process.exit(0);
   }
   switch (command || "init") {

package/package.json

@@ -18,5 +18,5 @@
     "unlink:cli": "npm unlink -g @basestream/cli"
   },
   "type": "module",
-  "version": "0.2.1"
+  "version": "0.2.2"
 }