@jeffober/thatch 0.1.15 → 0.1.17

package/src/prompts.ts

@@ -6,7 +6,8 @@ knowledge so future sessions can build on what you've already learned.
 
 Tools: thatch_memory_remember, thatch_memory_recall, thatch_memory_list,
        thatch_memory_show, thatch_memory_forget, thatch_store_list,
-       thatch_find_duplicates, thatch_dedup_mark_checked
+       thatch_find_duplicates, thatch_dedup_mark_checked,
+       thatch_extraction_done
 
 ## Stores
 
@@ -34,11 +35,16 @@ workflows. The host auto-discovers them, but reach for them proactively:
 
 - \`thatch-code-review\` — full multi-agent code review (dispatches 6 specialists + synthesizer). Requires sub-agent support.
 - \`thatch-workflow-research\` — research code workflows affected by a change or planned change, before reviewing or planning.
+- \`thatch-change-walkthrough\` — produces a teaching walkthrough of a diff with a specific format (SYNOPSIS + per-workflow orient/mechanism/numbered-stages + change overlay mirroring the same numbers) and calibrated prose rules. Load the skill for the format and prose rules, not just for the research method.
+- \`thatch-code-walkthrough\` — produces a teaching walkthrough for a feature/workflow as it stands today with a specific format (SYNOPSIS + per-workflow orient/mechanism/numbered-stages + Key files) and calibrated prose rules. Also use proactively to draft high-level docs for new or undocumented features (suitable for pkg/README.md or docs/features/<name>.md). Load the skill for the format and prose rules, not just for the research method.
 - \`thatch-review-context\` — gather project context (PRs, tickets, TODOs, deferred work) before a review.
 - \`thatch-project-primer\` — investigate a new project and write foundational memories.
 - \`thatch-session-reflection\` — record what you learned at end of session.
 - \`thatch-fact-extractor\` — extract durable facts from recent tool interactions (auto-triggered by the extraction pipeline).
 - \`thatch-dedup-classifier\` — resolve duplicate memory pairs from \`thatch_find_duplicates\`.
+- \`pr-description\` — draft a PR description using instructional-design scaffolding with bold and italic emphasis on the phrases that carry the meaning, so a reviewer skimming only the emphasized fragments still gets the story.
+- \`ticket-description\` — draft a ticket, issue, or work item (Linear or Jira) using instructional-design scaffolding with bold and italic emphasis for scanning.
+- \`split-overlarge-pr\` — split already-completed work from an overlarge PR into human-reviewable, release-safe PRs targeting main.
 
 ## When to Write
 
@@ -46,6 +52,14 @@ workflows. The host auto-discovers them, but reach for them proactively:
 Save immediately on: feedback, preferences, corrections, emotional signals,
 new project knowledge, conventions, architectural decisions, investigation results.
 
+## Before Responding
+
+Before composing a final response after substantial work this turn — multiple
+rounds of tool calls for investigation, debugging, or code-writing — check
+whether you've discovered knowledge worth persisting. Use thatch_memory_recall
+to check for duplicates, then thatch_memory_remember for new findings. Then
+deliver your response.
+
 ## What to Store
 
 - **Global store**: user observations, agent personality, system environment
@@ -164,12 +178,17 @@ Thatch ships skills for code review, project investigation, and memory
 workflows. The host auto-discovers them, but reach for them proactively:
 
 - \`thatch-workflow-research\` — research code workflows affected by a change or planned change, before reviewing or planning.
+- \`thatch-change-walkthrough\` — produces a teaching walkthrough of a diff with a specific format (SYNOPSIS + per-workflow orient/mechanism/numbered-stages + change overlay mirroring the same numbers) and calibrated prose rules. Load the skill for the format and prose rules, not just for the research method.
+- \`thatch-code-walkthrough\` — produces a teaching walkthrough for a feature/workflow as it stands today with a specific format (SYNOPSIS + per-workflow orient/mechanism/numbered-stages + Key files) and calibrated prose rules. Also use proactively to draft high-level docs for new or undocumented features (suitable for pkg/README.md or docs/features/<name>.md). Load the skill for the format and prose rules, not just for the research method.
 - \`thatch-review-context\` — gather project context (PRs, tickets, TODOs, deferred work) before a review.
 - \`thatch-review-pedantic\` / \`-acceptance\` / \`-state-flow\` / \`-no-slop\` / \`-breadcrumbs\` / \`-mark-and-sweep\` — six specialist review lenses. Run individually, then \`thatch-review-synthesizer\` to verify and aggregate.
 - \`thatch-project-primer\` — investigate a new project and write foundational memories.
 - \`thatch-session-reflection\` — record what you learned at end of session.
 - \`thatch-fact-extractor\` — extract durable facts from recent tool interactions (auto-triggered by the extraction pipeline).
 - \`thatch-dedup-classifier\` — resolve duplicate memory pairs from \`find_duplicates\`.
+- \`pr-description\` — draft a PR description using instructional-design scaffolding with bold and italic emphasis on the phrases that carry the meaning, so a reviewer skimming only the emphasized fragments still gets the story.
+- \`ticket-description\` — draft a ticket, issue, or work item (Linear or Jira) using instructional-design scaffolding with bold and italic emphasis for scanning.
+- \`split-overlarge-pr\` — split already-completed work from an overlarge PR into human-reviewable, release-safe PRs targeting main.
 
 ## When to Write
 
@@ -177,6 +196,14 @@ workflows. The host auto-discovers them, but reach for them proactively:
 Save immediately on: feedback, preferences, corrections, emotional signals,
 new project knowledge, conventions, architectural decisions, investigation results.
 
+## Before Responding
+
+Before composing a final response after substantial work this turn — multiple
+rounds of tool calls for investigation, debugging, or code-writing — check
+whether you've discovered knowledge worth persisting. Use memory_recall to
+check for duplicates, then memory_remember for new findings. Then deliver
+your response.
+
 ## What to Store
 
 - **Global store**: user observations, agent personality, system environment
@@ -357,12 +384,17 @@ Thatch ships skills for code review, project investigation, and memory
 workflows. The host auto-discovers them, but reach for them proactively:
 
 - \`thatch-workflow-research\` — research code workflows affected by a change or planned change, before reviewing or planning.
+- \`thatch-change-walkthrough\` — produces a teaching walkthrough of a diff with a specific format (SYNOPSIS + per-workflow orient/mechanism/numbered-stages + change overlay mirroring the same numbers) and calibrated prose rules. Load the skill for the format and prose rules, not just for the research method.
+- \`thatch-code-walkthrough\` — produces a teaching walkthrough for a feature/workflow as it stands today with a specific format (SYNOPSIS + per-workflow orient/mechanism/numbered-stages + Key files) and calibrated prose rules. Also use proactively to draft high-level docs for new or undocumented features (suitable for pkg/README.md or docs/features/<name>.md). Load the skill for the format and prose rules, not just for the research method.
 - \`thatch-review-context\` — gather project context (PRs, tickets, TODOs, deferred work) before a review.
 - \`thatch-review-pedantic\` / \`-acceptance\` / \`-state-flow\` / \`-no-slop\` / \`-breadcrumbs\` / \`-mark-and-sweep\` — six specialist review lenses. Run individually, then \`thatch-review-synthesizer\` to verify and aggregate.
 - \`thatch-project-primer\` — investigate a new project and write foundational memories.
 - \`thatch-session-reflection\` — record what you learned at end of session.
 - \`thatch-fact-extractor\` — extract durable facts from recent tool interactions (auto-triggered by the extraction pipeline).
 - \`thatch-dedup-classifier\` — resolve duplicate memory pairs from \`find_duplicates\`.
+- \`pr-description\` — draft a PR description using instructional-design scaffolding with bold and italic emphasis on the phrases that carry the meaning, so a reviewer skimming only the emphasized fragments still gets the story.
+- \`ticket-description\` — draft a ticket, issue, or work item (Linear or Jira) using instructional-design scaffolding with bold and italic emphasis for scanning.
+- \`split-overlarge-pr\` — split already-completed work from an overlarge PR into human-reviewable, release-safe PRs targeting main.
 
 ## When to Write
 
@@ -370,6 +402,14 @@ workflows. The host auto-discovers them, but reach for them proactively:
 Save immediately on: feedback, preferences, corrections, emotional signals,
 new project knowledge, conventions, architectural decisions, investigation results.
 
+## Before Responding
+
+Before composing a final response after substantial work this turn — multiple
+rounds of tool calls for investigation, debugging, or code-writing — check
+whether you've discovered knowledge worth persisting. Use memory_recall to
+check for duplicates, then memory_remember for new findings. Then deliver
+your response.
+
 ## What to Store
 
 - **Global store**: user observations, agent personality, system environment

package/src/setup.ts

@@ -173,7 +173,7 @@ function writeHooks(path: string, thatchBin: string): void {
   // (see src/extract-queue.ts). No stdout — the next model call must not block
   // on a payload that should be invisible to the agent until UserPromptSubmit.
   const bufferCmd = `${thatchBin} buffer-batch`;
-  // UserPromptSubmit drains the queue. With buffered interactions, it prints
+  // UserPromptSubmit peeks the queue. With buffered interactions, it prints
   // the extraction nudge carrying the JSON payload; with an empty queue, it
   // falls back to the static write-nudge. Either output is transcript-visible
   // since UserPromptSubmit adds stdout to context.

package/src/skills.ts

@@ -16,11 +16,14 @@ function loadSkillFile(name: string): string {
   const artifactsDir = join(__dirname, "..", "artifacts", "skills");
   const filePath = join(artifactsDir, name + ".md");
   const raw = readFileSync(filePath, "utf8");
-  // Interpolate REVIEW_COMMON
-  if (raw.includes("${REVIEW_COMMON}")) {
+  // Interpolate REVIEW_COMMON only when it appears on its own line (the
+  // directive form used by review specialist skills). Inline mentions in
+  // other skills (e.g. as examples in prose) are content, not directives,
+  // and must not be interpolated.
+  if (/^[ \t]*\$\{REVIEW_COMMON\}[ \t]*$/m.test(raw)) {
     const commonPath = join(artifactsDir, "common.md");
     const commonContent = readFileSync(commonPath, "utf8");
-    return raw.replace(/\$\{REVIEW_COMMON\}/g, commonContent);
+    return raw.replace(/^[ \t]*\$\{REVIEW_COMMON\}[ \t]*$/gm, commonContent);
   }
   return raw;
 }
@@ -39,7 +42,12 @@ function loadSharedSkills(): SkillDef[] {
     "thatch-review-synthesizer",
     "thatch-review-context",
     "thatch-workflow-research",
+    "thatch-change-walkthrough",
+    "thatch-code-walkthrough",
     "thatch-session-reflection",
+    "pr-description",
+    "ticket-description",
+    "split-overlarge-pr",
   ];
   return names.map((name) => ({ name, content: loadSkillFile(name) }));
 }