@trim21/personal-pi-extensions 0.0.305 → 0.0.308

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trim21/personal-pi-extensions",
-  "version": "0.0.305",
+  "version": "0.0.308",
   "type": "module",
   "description": "Custom pi coding-agent extensions: bwrap sandbox, workspace guard, opencode edit, and more",
   "keywords": [
@@ -93,6 +93,6 @@
     "web-tree-sitter": "^0.26.12"
   },
   "optionalDependencies": {
-    "@cortexkit/aft-linux-x64": "0.51.0"
+    "@cortexkit/aft-linux-x64": "0.51.2"
   }
 }

package/src/aft/ast-edit.ts

@@ -11,7 +11,11 @@
  * 防呆不同，ast_edit 不要求先读）。
  */
 
-import type { ExtensionAPI } from "@earendil-works/pi-coding-agent";
+import {
+  type ExtensionAPI,
+  generateDiffString,
+  generateUnifiedPatch,
+} from "@earendil-works/pi-coding-agent";
 import { Type } from "typebox";
 import { Value } from "typebox/value";
 
@@ -114,6 +118,35 @@ export function mapEditItems(
   });
 }
 
+/**
+ * 参照 Edit 工具的结果输出：把 preview 的 before/after 转成行号 diff、
+ * unified patch 与首个变更行。多文件（glob 批量）时逐文件拼接 diff/patch，
+ * firstChangedLine 取首个文件的。
+ */
+export function buildEditDiffDetails(
+  previewFiles: PreviewFile[],
+  fallbackFile: string,
+): { diff: string; patch: string; firstChangedLine: number | undefined } {
+  const parts = previewFiles.map((f) => {
+    const file = f.file || fallbackFile;
+    const diff = generateDiffString(f.before, f.after);
+    return {
+      file,
+      diff: diff.diff,
+      patch: generateUnifiedPatch(file, f.before, f.after),
+      firstChangedLine: diff.firstChangedLine,
+    };
+  });
+  if (parts.length === 0) {
+    return { diff: "", patch: "", firstChangedLine: undefined };
+  }
+  return {
+    diff: parts.map((p) => `--- ${p.file}\n${p.diff}`).join("\n"),
+    patch: parts.map((p) => `--- ${p.file}\n${p.patch}`).join("\n"),
+    firstChangedLine: parts[0]?.firstChangedLine,
+  };
+}
+
 // ── 工具 ────────────────────────────────────────────────────────────────────
 
 const EditItemParams = Type.Object({
@@ -262,6 +295,7 @@ export function registerAstEditTool(pi: ExtensionAPI, ctx: AftToolContext): void
         content: [{ type: "text", text }],
         details: {
           files,
+          ...buildEditDiffDetails(previewFiles, filePath),
           pendant: {
             markdown: buildPendantMarkdown({
               title: "ast_edit",

package/src/system-prompt/prompt.md

@@ -17,6 +17,7 @@ In addition to the tools above, you may have access to other custom tools depend
 
 ## Doing tasks
 
+- When investigating a codebase, first use the AFT tools (aft_outline / aft_zoom / aft_callgraph / aft_search) to map the structure, inspect named symbols, and trace call relationships before falling back to grep or full-file reads — they are cheaper and purpose-built for this.
 - The user will primarily request you to perform software engineering tasks. These may include solving bugs, adding new functionality, refactoring code, explaining code, and more. When given an unclear or generic instruction, consider it in the context of these software engineering tasks and the current working directory. For example, if the user asks you to change "methodName" to snake case, do not reply with just "method_name", instead find the method in the code and modify the code.
 - You are highly capable and often allow users to complete ambitious tasks that would otherwise be too complex or take too long. You should defer to user judgement about whether a task is too large to attempt.
 - For exploratory questions ("what could we do about X?", "how should we approach this?", "what do you think?"), respond in 2-3 sentences with a recommendation and the main tradeoff. Present it as something the user can redirect, not a decided plan. Don't implement until the user agrees.