@f5xc-salesdemos/xcsh 2.2.0 → 14.0.2

package/src/prompts/tools/hashline.md

@@ -0,0 +1,131 @@
+Applies precise file edits using `LINE#ID` anchors from `read` output.
+
+Read the file first. Copy anchors exactly from the latest `read` output. In one `edit` call, batch all edits for one file. After any successful edit, re-read before editing that file again.
+
+<operations>
+**Top level**
+- `path` — file path
+- `move` — optional rename target
+- `delete` — optional whole-file delete
+- `edits` — array of `{ loc, content }` entries
+
+**Edit entry**: `{ loc, content }`
+- `loc` — where to apply the edit (see below)
+- `content` — replacement/inserted lines (array of strings preferred, `null` to delete)
+
+**`loc` values**
+- `"append"` / `"prepend"` — insert at end/start of file
+- `{ append: "N#ID" }` / `{ prepend: "N#ID" }` — insert after/before anchored line
+- `{ range: { pos: "N#ID", end: "N#ID" } }` — replace inclusive range of lines `pos..end` with new content
+  </operations>
+
+<examples>
+All examples below reference the same file:
+```ts title="a.ts"
+{{hline  1 "// @ts-ignore"}}
+{{hline  2 "const timeout = 5000;"}}
+{{hline  3 "const tag = \"DO NOT SHIP\";"}}
+{{hline  4 ""}}
+{{hline  5 "function alpha() {"}}
+{{hline  6 "\tlog();"}}
+{{hline  7 "}"}}
+{{hline  8 ""}}
+{{hline  9 "function beta() {"}}
+{{hline 10 "\t// TODO: remove after migration"}}
+{{hline 11 "\tlegacy();"}}
+{{hline 12 "\ttry {"}}
+{{hline 13 "\t\treturn parse(data);"}}
+{{hline 14 "\t} catch (err) {"}}
+{{hline 15 "\t\tconsole.error(err);"}}
+{{hline 16 "\t\treturn null;"}}
+{{hline 17 "\t}"}}
+{{hline 18 "}"}}
+```
+
+<example name="replace a block body">
+Replace only the catch body. Do not target the shared boundary line `} catch (err) {`.
+```
+{
+  path: "a.ts",
+  edits: [{
+    loc: { range: { pos: {{href 15 "\t\tconsole.error(err);"}}, end: {{href 16 "\t\treturn null;"}} } },
+    content: [
+      "\t\tif (isEnoent(err)) return null;",
+      "\t\tthrow err;"
+    ]
+  }]
+}
+```
+</example>
+
+<example name="replace whole block including closing brace">
+Replace the entire body of `alpha`, including its closing `}`. `end` **MUST** be {{href 7 "}"}} because `content` includes `}`.
+```
+{
+  path: "a.ts",
+  edits: [{
+    loc: { range: { pos: {{href 6 "\tlog();"}}, end: {{href 7 "}"}} } },
+    content: [
+      "\tvalidate();",
+      "\tlog();",
+      "}"
+    ]
+  }]
+}
+```
+**Wrong**: using `end: {{href 6 "\tlog();"}}` with the same content — line 7 (`}`) survives the replacement AND content emits `}`, producing two closing braces.
+</example>
+
+<example name="replace one line">
+```
+{
+  path: "a.ts",
+  edits: [{
+    loc: { range: { pos: {{href 2 "const timeout = 5000;"}}, end: {{href 2 "const timeout = 5000;"}} } },
+    content: ["const timeout = 30_000;"]
+  }]
+}
+```
+</example>
+
+<example name="delete a range">
+```
+{
+  path: "a.ts",
+  edits: [{
+    loc: { range: { pos: {{href 10 "\t// TODO: remove after migration"}}, end: {{href 11 "\tlegacy();"}} } },
+    content: null
+  }]
+}
+```
+</example>
+
+<example name="insert before sibling">
+When adding a sibling declaration, prefer `prepend` on the next declaration.
+```
+{
+  path: "a.ts",
+  edits: [{
+    loc: { prepend: {{href 9 "function beta() {"}} },
+    content: [
+      "function gamma() {",
+      "\tvalidate();",
+      "}",
+      ""
+    ]
+  }]
+}
+```
+</example>
+</examples>
+
+<critical>
+- Make the minimum exact edit. Do not rewrite nearby code unless the consumed range requires it.
+- Use anchors exactly as `N#ID` from the latest `read` output.
+- `range` requires both `pos` and `end`.
+- When your replacement `content` ends with a closing delimiter (`}`, `*/`, `)`, `]`), verify `end` includes the original line carrying that delimiter. If `end` stops one line too early, the original delimiter survives and your content adds a second copy.
+- **Self-check**: compare the last line of `content` with the line immediately after `end` in the file. If they match (e.g., both are `}`), extend `end` to include that line.
+- For a range, either replace only the body or replace the whole range. Do not split range boundaries.
+- `content` must be literal file content with matching indentation. If the file uses tabs, use real tabs.
+- You **MUST NOT** use this tool to reformat or clean up unrelated code. **ALWAYS** use project-specific tooling like linters or code formatters which are much more efficient and reliable.
+  </critical>

package/src/prompts/tools/inspect-image-system.md

@@ -0,0 +1,20 @@
+You are an image-analysis assistant.
+
+Core behavior:
+- Be evidence-first: distinguish direct observations from inferences.
+- If something is unclear, say uncertain rather than guessing.
+- Do not fabricate unreadable or occluded details.
+- Keep output compact and useful.
+
+Default output format (unless the requested question asks for another format):
+1) Answer
+2) Key evidence
+3) Caveats / uncertainty
+
+For OCR-style requests:
+- Preserve exact visible text, including casing and punctuation.
+- If text is partially unreadable, mark the unreadable segments explicitly.
+
+For UI/screenshot debugging requests:
+- Focus on visible states, labels, toggles, error messages, disabled controls, and relevant affordances.
+- Separate observed UI state from probable root cause.

package/src/prompts/tools/inspect-image.md

@@ -0,0 +1,32 @@
+Inspects an image file with a vision-capable model and returns compact text analysis.
+
+<instruction>
+- Use this for image understanding tasks (OCR, UI/screenshot debugging, scene/object questions)
+- Provide `path` to the local image file
+- Write a specific `question`:
+  - what to inspect
+  - constraints (for example: "quote visible text verbatim", "only report confirmed findings")
+  - desired output format (bullets/table/JSON/short answer)
+- Keep `question` grounded in observable evidence and ask for uncertainty when details are unclear
+- Use this tool over `read` when the goal is image analysis
+</instruction>
+
+<examples>
+- OCR with strict formatting:
+  - `{"path":"screenshots/error.png","question":"Extract all visible text verbatim. Return as bullet list in reading order."}`
+- Screenshot debugging:
+  - `{"path":"screenshots/settings.png","question":"Identify the likely cause of the disabled Save button. Return: (1) observations, (2) likely cause, (3) confidence."}`
+- Scene/object question:
+  - `{"path":"photos/shelf.jpg","question":"List all clearly visible product labels and their shelf positions (top/middle/bottom). If unreadable, say unreadable."}`
+</examples>
+
+<output>
+- Returns text-only analysis from the vision model
+- No image content blocks are returned in tool output
+</output>
+
+<critical>
+- Parameters are strict: only `path` and `question` are allowed
+- If image submission is blocked by settings, the tool will fail with an actionable error
+- If configured model does not support image input, configure a vision-capable model role before retrying
+</critical>

package/src/prompts/tools/lsp.md

@@ -0,0 +1,33 @@
+Interacts with Language Server Protocol servers for code intelligence.
+
+<operations>
+- `diagnostics`: Get errors/warnings for a file, a glob of files, or the entire workspace (`file: "*"`)
+- `definition`: Go to symbol definition → file path + position + 3-line source context
+- `type_definition`: Go to symbol type definition → file path + position + 3-line source context
+- `implementation`: Find concrete implementations → file path + position + 3-line source context
+- `references`: Find references → locations with 3-line source context (first 50), remaining location-only
+- `hover`: Get type info and documentation → type signature + docs
+- `symbols`: List symbols in a file, or search workspace with `file: "*"` and a `query`
+- `rename`: Rename symbol across codebase → preview or apply edits
+- `code_actions`: List available quick-fixes/refactors/import actions; apply one when `apply: true` and `query` matches title or index
+- `status`: Show active language servers
+- `reload`: Restart a specific server (via `file`) or all servers with `file: "*"`
+</operations>
+
+<parameters>
+- `file`: File path, glob pattern (e.g. `src/**/*.ts`), or `"*"` for workspace scope. Globs are expanded locally before dispatch. `"*"` routes `diagnostics`/`symbols`/`reload` to their workspace-wide form.
+- `line`: 1-indexed line number for position-based actions
+- `symbol`: Substring on the target line used to resolve column automatically
+- `occurrence`: 1-indexed match index when `symbol` appears multiple times on the same line
+- `query`: Symbol search query, code-action kind filter (list mode), or code-action selector (apply mode)
+- `new_name`: Required for rename
+- `apply`: Apply edits for rename/code_actions (default true for rename, list mode for code_actions unless explicitly true)
+- `timeout`: Request timeout in seconds (clamped to 5-60, default 20)
+</parameters>
+
+<caution>
+- Requires running LSP server for target language
+- Some operations require file to be saved to disk
+- Glob expansion samples up to 20 files per request; use `file: "*"` for broader coverage
+- When `symbol` is provided for position-based actions, missing symbols or out-of-bounds `occurrence` values return an explicit error instead of silently falling back
+</caution>

package/src/prompts/tools/patch.md

@@ -0,0 +1,72 @@
+Patches files given diff hunks. Primary tool for existing-file edits.
+
+<instruction>
+**Hunk Headers:**
+- `@@` — bare header when context lines unique
+- `@@ $ANCHOR` — anchor copied verbatim from file (full line or unique substring)
+**Anchor Selection:**
+1. Otherwise choose highly specific anchor copied from file:
+   - full function signature
+   - class declaration
+   - unique string literal/error message
+   - config key with uncommon name
+2. On "Found multiple matches": add context lines, use multiple hunks with separate anchors, or use longer anchor substring
+**Context Lines:**
+Use enough ` `-prefixed lines to make match unique (usually 2–8)
+When editing structured blocks (nested braces, tags, indented regions), include opening and closing lines so edit stays inside block
+</instruction>
+
+<parameters>
+```ts
+type T =
+   // Diff is one or more hunks in the same file.
+   // - Each hunk begins with "@@" (anchor optional).
+   // - Each hunk body only has lines starting with ' ' | '+' | '-'.
+   // - Each hunk includes at least one change (+ or -).
+   | { path: string, op: "update", diff: string }
+   // Diff is full file content, no prefixes.
+   | { path: string, op: "create", diff: string }
+   // No diff for delete.
+   | { path: string, op: "delete" }
+   // New path for update+move.
+   | { path: string, op: "update", rename: string, diff: string }
+```
+</parameters>
+
+<output>
+Returns success/failure; on failure, error message indicates:
+- "Found multiple matches" — anchor/context not unique enough
+- "No match found" — context lines don't exist in file (wrong content or stale read)
+- Syntax errors in diff format
+</output>
+
+<critical>
+- You **MUST** read the target file before editing
+- You **MUST** copy anchors and context lines verbatim (including whitespace)
+- You **MUST NOT** use anchors as comments (no line numbers, location labels, placeholders like `@@ @@`)
+- You **MUST NOT** place new lines outside the intended block
+- If edit fails or breaks structure, you **MUST** re-read the file and produce a new patch from current content — you **MUST NOT** retry the same diff
+- **NEVER** use edit to fix indentation, whitespace, or reformat code. Formatting is a single command run once at the end (`bun fmt`, `cargo fmt`, `prettier —write`, etc.)—not N individual edits. If you see inconsistent indentation after an edit, leave it; the formatter will fix all of it in one pass.
+</critical>
+
+<example name="create">
+edit {"path":"hello.txt","op":"create","diff":"Hello\n"}
+</example>
+
+<example name="update">
+edit {"path":"src/app.py","op":"update","diff":"@@ def greet():\n def greet():\n-print('Hi')\n+print('Hello')\n"}
+</example>
+
+<example name="rename">
+edit {"path":"src/app.py","op":"update","rename":"src/main.py","diff":"@@\n …\n"}
+</example>
+
+<example name="delete">
+edit {"path":"obsolete.txt","op":"delete"}
+</example>
+
+<avoid>
+- Generic anchors: `import`, `export`, `describe`, `function`, `const`
+- Repeating same addition in multiple hunks (duplicate blocks)
+- Full-file overwrites for minor changes (acceptable for major restructures or short files)
+</avoid>

package/src/prompts/tools/python.md

@@ -0,0 +1,60 @@
+Runs Python cells sequentially in persistent IPython kernel.
+
+<instruction>
+Kernel persists across calls and cells; **imports, variables, and functions survive—use this.**
+**Work incrementally:**
+- You **SHOULD** use one logical step per cell (imports, define function, test it, use it)
+- You **SHOULD** pass multiple small cells in one call
+- You **SHOULD** define small functions you can reuse and debug individually
+- You **MUST** put workflow explanations in assistant message or cell title
+**When something fails:**
+- Errors tell you which cell failed (e.g., "Cell 3 failed")
+- You **SHOULD** resubmit only the fixed cell (or fixed cell + remaining cells)
+</instruction>
+
+{{#if categories.length}}
+<prelude>
+All helpers auto-print results and return values for chaining.
+
+{{#each categories}}
+### {{name}}
+
+```
+{{#each functions}}
+{{name}}{{signature}}
+    {{docstring}}
+{{/each}}
+```
+{{/each}}
+</prelude>
+{{/if}}
+
+<output>
+User sees output like Jupyter notebook; rich displays render fully:
+- `display(JSON(data))` → interactive JSON tree
+- `display(HTML(…))` → rendered HTML
+- `display(Markdown(…))` → formatted markdown
+- `plt.show()` → inline figures
+  **You will see object repr** (e.g., `<IPython.core.display.JSON object>`). Trust `display()`; you **MUST NOT** assume user sees only repr.
+</output>
+
+<caution>
+- Per-call mode uses fresh kernel each call
+- You **MUST** use `reset: true` to clear state when session mode active
+</caution>
+
+<critical>
+- You **MUST** use `run()` for shell commands; you **MUST NOT** use raw `subprocess`
+</critical>
+
+<example name="good">
+```python
+# Multiple small cells
+cells: [
+    {"title": "imports", "code": "import json\nfrom pathlib import Path"},
+    {"title": "parse helper", "code": "def parse_config(path):\n    return json.loads(Path(path).read_text())"},
+    {"title": "test helper", "code": "parse_config('config.json')"},
+    {"title": "use helper", "code": "configs = [parse_config(p) for p in Path('.').glob('*.json')]"}
+]
+```
+</example>

package/src/prompts/tools/read-chunk.md

@@ -0,0 +1,17 @@
+Reads files using syntax-aware chunks.
+
+<instruction>
+- `path` — file path or URL; may include `:selector` suffix
+- `sel` — optional selector: `class_Foo`, `class_Foo.fn_bar#ABCD@body`, `?`, `L50`, `L50-L120`, or `raw`
+- `timeout` — seconds, for URLs only
+
+Each opening anchor `[< full.chunk.path#CCCC ]` in the default output identifies a chunk. Use `full.chunk.path#CCCC` as-is to read truncated chunks.
+If you need a canonical target list, run `read(path="file", sel="?")`. That listing shows chunk paths with CRCs.
+Line numbers in the gutter are absolute file line numbers.
+
+Chunk trees: JS, TS, TSX, Python, Rust, Go. Others use blank-line fallback.
+</instruction>
+
+<critical>
+- **MUST** `read` before editing — never invent chunk names or CRCs.
+</critical>

package/src/prompts/tools/read.md

@@ -0,0 +1,54 @@
+Reads the content at the specified path or URL.
+
+<instruction>
+The `read` tool is a multi-purpose tool that can be used to inspect all kinds of files and URLs.
+- You **MUST** parallelize reads when exploring related files
+
+## Parameters
+- `path` -- file path or URL (required)
+- `sel` -- optional selector for line ranges or raw mode
+- `timeout` -- seconds, for URLs only
+
+## Selectors
+
+|`sel` value|Behavior|
+|---|---|
+|*(omitted)*|Read full file (up to {{DEFAULT_LIMIT}} lines)|
+|`L50`|Read from line 50 onward|
+|`L50-L120`|Read lines 50 through 120|
+|`raw`|Raw content without transformations (for URLs: untouched HTML)|
+
+Max {{DEFAULT_MAX_LINES}} lines per call.
+
+# Filesystem
+{{#if IS_HASHLINE_MODE}}
+- If reading from FS, result will be prefixed with anchors: `41#ZZ:def alpha():`
+{{else}}
+  {{#if IS_LINE_NUMBER_MODE}}
+- If reading from FS, result will be prefixed with line numbers: `41:def alpha():`
+  {{/if}}
+{{/if}}
+
+# Inspection
+When used with a PDF, Word, PowerPoint, Excel, RTF, EPUB, or Jupyter notebook file, the tool will return the extracted text.
+It can also be used to inspect images.
+
+# Directories & Archives
+When used against a directory, or an archive root, the tool will return a list of directory entries within.
+- Formats: `.tar`, `.tar.gz`, `.tgz`, and `.zip`.
+- Use `archive.ext:path/inside/archive` to read or list archive contents
+
+# URLs
+- Extract information from web pages, GitHub issues/PRs, Stack Overflow, Wikipedia, Reddit, NPM, arXiv, technical blogs, RSS/Atom feeds, JSON endpoints
+- `sel="raw"` for untouched HTML or debugging
+- `timeout` to override the default request timeout
+</instruction>
+
+<critical>
+- You **MUST** use `read` instead of bash for ALL file reading: `cat`, `head`, `tail`, `less`, `more` are FORBIDDEN.
+- You **MUST** use `read` instead of `ls` for directory listings.
+- You **MUST** use `read` instead of shelling out to `tar` or `unzip` for supported archive reads.
+- You **MUST** always include the `path` parameter, NEVER call `read` with empty arguments `{}`.
+- When reading specific line ranges, use `sel`: `read(path="file", sel="L50-L150")` not `cat -n file | sed`.
+- You **MAY** use `sel` with URL reads; the tool will paginate the cached fetched output.
+</critical>

package/src/prompts/tools/render-mermaid.md

@@ -0,0 +1,9 @@
+Convert Mermaid graph source into ASCII diagram output.
+
+Parameters:
+- `mermaid` (required): Mermaid graph text to render.
+- `config` (optional): JSON render configuration (spacing and layout options).
+Behavior:
+- Returns ASCII diagram text.
+- Saves full ASCII output to an artifact URL (`artifact://<id>`) when artifact storage is available.
+- Returns an error when the Mermaid input is invalid or rendering fails.

package/src/prompts/tools/replace.md

@@ -0,0 +1,36 @@
+Performs string replacements in files with fuzzy whitespace matching.
+
+<instruction>
+- You **MUST** use the smallest edit that uniquely identifies the change
+- If `old_text` not unique, you **MUST** expand to include more context or use `all: true` to replace all occurrences
+- Fuzzy matching handles minor whitespace/indentation differences automatically
+- You **SHOULD** prefer editing existing files over creating new ones
+</instruction>
+
+<output>
+Returns success/failure status. On success, file modified in place with replacement applied. On failure (e.g., `old_text` not found or matches multiple locations without `all: true`), returns error describing issue.
+</output>
+
+<critical>
+- You **MUST** read the file at least once in the conversation before editing. Tool errors if you attempt edit without reading file first.
+</critical>
+
+<bash-alternatives>
+Replace for content-addressed changes—you identify \_what* to change by its text.
+
+For position-addressed or pattern-addressed changes, bash more efficient:
+
+|Operation|Command|
+|---|---|
+|Append to file|`cat >> file <<'EOF'`…`EOF`|
+|Prepend to file|`{ cat - file; } <<'EOF' > tmp && mv tmp file`|
+|Delete lines N-M|`sed -i 'N,Md' file`|
+|Insert after line N|`sed -i 'Na\text' file`|
+|Regex replace|`sd 'pattern' 'replacement' file`|
+|Bulk replace across files|`sd 'pattern' 'replacement' **/*.ts`|
+|Copy lines N-M to another file|`sed -n 'N,Mp' src >> dest`|
+|Move lines N-M to another file|`sed -n 'N,Mp' src >> dest && sed -i 'N,Md' src`|
+
+Use Replace when _content itself_ identifies location.
+Use bash when _position_ or _pattern_ identifies what to change.
+</bash-alternatives>

package/src/prompts/tools/resolve.md

@@ -0,0 +1,8 @@
+Resolves a pending preview action by either applying or discarding it.
+- `action` is required:
+  - `"apply"` persists the pending changes.
+  - `"discard"` rejects the pending changes.
+- `reason` is required and must explain why you chose to apply or discard.
+
+This tool is only valid when a pending action exists (typically after a preview step).
+If no pending action exists, the call fails with an error.

package/src/prompts/tools/rewind.md

@@ -0,0 +1,13 @@
+Ends an active checkpoint and rewinds context back to that checkpoint, replacing intermediate exploration with your report.
+
+Use this immediately after investigative work started with `checkpoint`.
+
+Requirements:
+- `report` is **REQUIRED** and must be concise, factual, and actionable.
+- Include key findings, decisions, and any unresolved risks.
+- Do not include raw scratch logs unless essential.
+- You **MUST** call this before yielding if a checkpoint is active.
+
+Behavior:
+- If no checkpoint is active, this tool errors.
+- On success, the session rewinds and keeps your report as retained context.

package/src/prompts/tools/search-tool-bm25.md

@@ -0,0 +1,34 @@
+Search hidden MCP tool metadata when MCP tool discovery is enabled.
+
+Use this tool to discover MCP tools that are loaded into the session but not exposed to the model by default.
+
+{{#if hasDiscoverableMCPServers}}Discoverable MCP servers in this session: {{#list discoverableMCPServerSummaries join=", "}}{{this}}{{/list}}.{{/if}}
+{{#if discoverableMCPToolCount}}Total discoverable MCP tools loaded: {{discoverableMCPToolCount}}.{{/if}}
+Input:
+- `query` — required natural-language or keyword query
+- `limit` — optional maximum number of tools to return and activate (default `8`)
+
+Behavior:
+- Searches hidden MCP tool metadata using BM25-style relevance ranking
+- Matches against MCP tool name, server name, description, and input schema keys
+- Activates the top matching MCP tools for the rest of the current session
+- Repeated searches add to the active MCP tool set; they do not remove earlier selections
+- Newly activated MCP tools become available before the next model call in the same overall turn
+
+Notes:
+- If you are unsure, start with `limit` between 5 and 10 to see a broader set of tools.
+- `query` is matched against MCP tool metadata fields:
+  - `name`
+  - `label`
+  - `server_name`
+  - `mcp_tool_name`
+  - `description`
+  - input schema property keys (`schema_keys`)
+
+This is not repository search, file search, or code search. Use it only for MCP tool discovery.
+
+Returns JSON with:
+- `query`
+- `activated_tools` — MCP tools activated by this search call
+- `match_count` — number of ranked matches returned by the search
+- `total_tools`

package/src/prompts/tools/ssh.md

@@ -0,0 +1,44 @@
+Runs commands on remote hosts.
+
+<instruction>
+You **MUST** build commands from the reference below
+</instruction>
+
+<commands>
+**linux/bash, linux/zsh, macos/bash, macos/zsh** — Unix-like:
+- Files: `ls`, `cat`, `head`, `tail`, `grep`, `find`
+- System: `ps`, `top`, `df`, `uname` (all), `free` (Linux only)
+- Navigation: `cd`, `pwd`
+**windows/bash, windows/sh** — Windows Unix layer (WSL, Cygwin, Git Bash):
+- Files/System/Navigation: same as Unix-like above, minus `free`
+**windows/powershell** — PowerShell:
+- Files: `Get-ChildItem`, `Get-Content`, `Select-String`
+- System: `Get-Process`, `Get-ComputerInfo`
+- Navigation: `Set-Location`, `Get-Location`
+**windows/cmd** — Command Prompt:
+- Files: `dir`, `type`, `findstr`, `where`
+- System: `tasklist`, `systeminfo`
+- Navigation: `cd`, `echo %CD%`
+</commands>
+
+<critical>
+You **MUST** verify the shell type from "Available hosts" and use matching commands.
+</critical>
+
+<example name="linux">
+Task: List /home/user files on "server1"
+Host: server1 (10.0.0.1) | linux/bash
+Command: `ls -la /home/user`
+</example>
+
+<example name="windows-cmd">
+Task: Show running processes on "winbox"
+Host: winbox (192.168.1.5) | windows/cmd
+Command: `tasklist /v`
+</example>
+
+<example name="macos">
+Task: Get system info on "macbook"
+Host: macbook (10.0.0.20) | macos/zsh
+Command: `uname -a && sw_vers`
+</example>

package/src/prompts/tools/task-summary.md

@@ -0,0 +1,28 @@
+<task-summary>
+<header>{{successCount}}/{{totalCount}} succeeded{{#if hasCancelledNote}} ({{cancelledCount}} cancelled){{/if}} [{{duration}}]</header>
+
+{{#each summaries}}
+<agent id="{{id}}" agent="{{agent}}">
+<status>{{status}}</status>
+{{#if meta}}<meta lines="{{meta.lineCount}}" size="{{meta.charSize}}" />{{/if}}
+{{#if truncated}}
+<preview full-path="agent://{{id}}">
+{{preview}}
+</preview>
+{{else}}
+<result>
+{{preview}}
+</result>
+{{/if}}
+</agent>
+{{#unless @last}}
+---
+{{/unless}}
+{{/each}}
+
+{{#if mergeSummary}}
+<merge-summary>
+{{mergeSummary}}
+</merge-summary>
+{{/if}}
+</task-summary>