@xynogen/pix-commands 0.1.2 → 0.1.4

package/README.md

@@ -1,10 +1,12 @@
 # pix-commands
 
-Pi extension — `/diff` and `/clear` slash commands.
+Pi extension — `/clear` slash command.
 
 ## What it does
 
-Registers two slash commands. `/diff` asks the agent to inspect `git status` and `git diff`, then respond with a one-sentence TL;DR, a per-file breakdown of what changed and why (with +/− line counts), and a brief impact note on behaviour or tests. If an agent turn is already in progress, the prompt is queued as a follow-up. `/clear` deletes `~/.cache/pi` — useful for flushing stale model-data or BenchLM cache — and prompts you to run `/reload` to apply the change. No extra dependencies beyond Pi.
+Registers the `/clear` slash command. `/clear` deletes `~/.cache/pi` — useful for flushing stale model-data or BenchLM cache — and prompts you to run `/reload` to apply the change. No extra dependencies beyond Pi.
+
+> Diff review moved to the `diff` skill in [`@xynogen/pix-skills`](https://github.com/xynogen/pix-mono/tree/main/packages/pix-skills), which pre-populates `git status` + staged/unstaged diffs via the `` !`cmd` `` directive.
 
 ## Install
 

package/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "@xynogen/pix-commands",
-	"version": "0.1.2",
-	"description": "Pi extension — /diff and /clear commands",
+	"version": "0.1.4",
+	"description": "Pi extension — /clear command",
 	"type": "module",
 	"main": "src/index.ts",
 	"scripts": {

package/src/extension.ts

@@ -1,11 +1,9 @@
 import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
 import registerClear from "./clear.ts";
-import registerDiff from "./diff.ts";
 import { once } from "./once.ts";
 
 export default function (pi: ExtensionAPI): void {
-	once("pix-commands", () => {
-		registerDiff(pi);
+	once(pi, "pix-commands", () => {
 		registerClear(pi);
 	});
 }

package/src/index.ts

@@ -1,2 +1 @@
 export { default as registerClear } from "./clear.ts";
-export { default as registerDiff } from "./diff.ts";

package/src/once.ts

@@ -1,15 +1,25 @@
 /**
- * Idempotency guard for extension activation.
+ * Per-instance idempotency guard for extension activation.
  *
- * pix-core (the meta-package) invokes this package's factory in addition to a
- * possible direct install. Pi's loader uses jiti with `moduleCache: false`, so
- * each load pass re-evaluates modules — a plain module-level flag would not be
- * shared. The dedupe key therefore lives on `globalThis`, which persists for
- * the lifetime of the process across all load passes.
+ * pix-core (the meta-package) invokes this package's factory, and a standalone
+ * install makes Pi invoke it again — sometimes against the SAME `pi`. We must
+ * dedupe that. But Pi rebuilds the extension runtime on /new, /resume, /fork,
+ * and /reload, handing the factory a BRAND-NEW `pi`; that must re-register.
+ *
+ * Keying the registry on the `pi` instance satisfies both: same instance =>
+ * skip, new instance => run. The registry lives on globalThis because jiti
+ * (`moduleCache: false`) re-evaluates this module on every load pass, so a
+ * module-scoped WeakMap would not be shared between the aggregator pass and the
+ * standalone pass within a single session.
  */
-export function once(key: string, fn: () => void): void {
-	const g = globalThis as { __pixLoaded?: Set<string> };
-	const loaded = (g.__pixLoaded ??= new Set<string>());
+export function once(pi: object, key: string, fn: () => void): void {
+	const g = globalThis as { __pixOnce?: WeakMap<object, Set<string>> };
+	const registry = (g.__pixOnce ??= new WeakMap<object, Set<string>>());
+	let loaded = registry.get(pi);
+	if (!loaded) {
+		loaded = new Set<string>();
+		registry.set(pi, loaded);
+	}
 	if (loaded.has(key)) return;
 	loaded.add(key);
 	fn();

package/src/diff.ts

@@ -1,38 +0,0 @@
-/**
- * /diff — summarise unstaged git diff: what changed, why, and impact.
- *
- * The agent runs `git status` + `git diff`, then replies with:
- *   1. One-line TL;DR of the overall change
- *   2. Per-file summary: what changed and why (not just counts)
- *   3. Brief impact note (behaviour change, bug fix, refactor, etc.)
- */
-
-import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
-
-const DIFF_PROMPT = `Run \`git status\` and \`git diff\` to inspect all unstaged changes, then respond with:
-
-**TL;DR** — one sentence: what is the overall change.
-
-**Per-file breakdown** — for each changed file:
-- Filename (+lines/-lines)
-- What changed (describe the actual code change)
-- Why it changed (intent / reason behind the edit)
-
-**Impact** — one sentence: what effect does this have on behaviour, tests, or users.
-
-Rules: base everything on the actual diff content. Use \`git diff --stat\` for line counts. Skip staged-only changes. Be concise — each file entry should fit in 1-2 lines.`;
-
-export default function (pi: ExtensionAPI) {
-	pi.registerCommand("diff", {
-		description:
-			"Summarise unstaged diff: TL;DR, per-file what/why/counts, impact",
-		handler: async (_args, ctx) => {
-			if (!ctx.isIdle()) {
-				pi.sendUserMessage(DIFF_PROMPT, { deliverAs: "followUp" });
-				ctx.ui.notify("Queued /diff after the current turn finishes.", "info");
-				return;
-			}
-			pi.sendUserMessage(DIFF_PROMPT);
-		},
-	});
-}