From 441302022ff0dcf7b9ec5131aca6a42b060e876e Mon Sep 17 00:00:00 2001 From: Martin Aeschlimann Date: Thu, 6 Nov 2025 12:31:52 +0100 Subject: [PATCH] set tools in savePrompt (#1820) --- extensions/copilot/assets/prompts/savePrompt.prompt.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/extensions/copilot/assets/prompts/savePrompt.prompt.md b/extensions/copilot/assets/prompts/savePrompt.prompt.md index fd36195332f..a2b8d81b9c8 100644 --- a/extensions/copilot/assets/prompts/savePrompt.prompt.md +++ b/extensions/copilot/assets/prompts/savePrompt.prompt.md @@ -1,14 +1,15 @@ --- name: savePrompt description: Generalize the current discussion into a reusable prompt and save it as a file +tools: [ 'edit', 'search' ] --- Generalize the current discussion into a reusable prompt that can be applied in similar contexts. Think step by step: 1. Review the conversation to identify the user's primary goal or task pattern -2. Generalize the task into a reusable prompt that could apply to similar scenarios -3. Extract the core intent, removing conversation-specific details (e.g., specific file names, variable names, or project-specific context) -4. If there is no discussion or no task to extract, give a one sentence response to the user that the `/savePrompt` prompt expects an active discussion to generalize. Keep the reply concise. +2. If there is no conversation present, reply to the user that the `/savePrompt` prompt expects an active discussion to generalize. Keep the reply concise. +3. Generalize the task into a reusable prompt that could apply to similar scenarios +4. Extract the core intent, removing conversation-specific details (e.g., specific file names, variable names, or project-specific context) 5. Craft the generalized multi-line markdown text prompt, using placeholders where appropriate (e.g., "the selected code", "the current file", "the specified functionality") 6. Create a very concise action-oriented title in camelCase format that will be used for the slash command (1-3 words, e.g., "generateUnitTests", "refactorForPerformance", "explainApiDesign", etc) 7. Write a brief description (1 sentence, max 15 words) explaining the goal of the prompt @@ -18,7 +19,7 @@ Think step by step: Here's an example of the expected output format: ``` --- -name: ${The concise title in kebab-case format. You can only use letters, digits, underscores, hyphens, and periods} +name: ${The concise title in camelCase format. You can only use letters, digits, underscores, hyphens, and periods} description: ${A brief description (1 sentence) explaining the goal of the prompt} argument-hint: ${A description of the expected inputs for the prompt, if any} ---