Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-03-23 01:25:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Revert "fetch -> web/fetch for everything"

Browse Source 
This reverts commit ca790b1716.
This commit is contained in:
Jon Corbin
2026-01-12 14:03:48 -05:00
parent e8577617b0
commit 5afc90e633
69 changed files with 360 additions and 360 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
agents/accessibility.agent.md
View File

@@ -1,7 +1,7 @@
---
description: 'Expert assistant for web accessibility (WCAG 2.1/2.2), inclusive UX, and a11y testing'
model: GPT-4.1
tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
---
# Accessibility Expert

2
agents/aem-frontend-specialist.agent.md
View File

@@ -1,7 +1,7 @@
---
description: 'Expert assistant for developing AEM components using HTL, Tailwind CSS, and Figma-to-code workflows with design system integration'
model: 'GPT-4.1'
tools: ['codebase', 'edit/editFiles', 'web/fetch', 'githubRepo', 'figma-dev-mode-mcp-server']
tools: ['codebase', 'edit/editFiles', 'fetch', 'githubRepo', 'figma-dev-mode-mcp-server']
---
# AEM Front-End Specialist

2
agents/bicep-implement.agent.md
View File

@@ -1,7 +1,7 @@
---
description: 'Act as an Azure Bicep Infrastructure as Code coding specialist that creates Bicep templates.'
tools:
[ 'edit/editFiles', 'web/fetch', 'runCommands', 'terminalLastCommand', 'get_bicep_best_practices', 'azure_get_azure_verified_module', 'todos' ]
[ 'edit/editFiles', 'fetch', 'runCommands', 'terminalLastCommand', 'get_bicep_best_practices', 'azure_get_azure_verified_module', 'todos' ]
---
# Azure Bicep Infrastructure as Code coding Specialist

2
agents/bicep-plan.agent.md
View File

@@ -1,7 +1,7 @@
---
description: 'Act as implementation planner for your Azure Bicep Infrastructure as Code task.'
tools:
[ 'edit/editFiles', 'web/fetch', 'microsoft-docs', 'azure_design_architecture', 'get_bicep_best_practices', 'bestpractices', 'bicepschema', 'azure_get_azure_verified_module', 'todos' ]
[ 'edit/editFiles', 'fetch', 'microsoft-docs', 'azure_design_architecture', 'get_bicep_best_practices', 'bestpractices', 'bicepschema', 'azure_get_azure_verified_module', 'todos' ]
---
# Azure Bicep Infrastructure Planning

2
agents/critical-thinking.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Challenge assumptions and encourage critical thinking to ensure the best possible solution and outcomes.'
tools: ['codebase', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'problems', 'search', 'searchResults', 'usages']
tools: ['codebase', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'problems', 'search', 'searchResults', 'usages']
---
# Critical thinking mode instructions

2
agents/csharp-dotnet-janitor.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.'
tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'microsoft.docs.mcp', 'github']
tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'microsoft.docs.mcp', 'github']
---
# C#/.NET Janitor

2
agents/custom-agent-foundry.agent.md
View File

@@ -24,7 +24,7 @@ When a user wants to create a custom agent, start by understanding:
### 2. Custom Agent Design Principles
**Tool Selection Strategy:**
- **Read-only agents** (planning, research, review): Use `['search', 'web/fetch', 'githubRepo', 'usages', 'grep_search', 'read_file', 'semantic_search']`
- **Read-only agents** (planning, research, review): Use `['search', 'fetch', 'githubRepo', 'usages', 'grep_search', 'read_file', 'semantic_search']`
- **Implementation agents** (coding, refactoring): Add `['replace_string_in_file', 'multi_replace_string_in_file', 'create_file', 'run_in_terminal']`
- **Testing agents**: Include `['run_notebook_cell', 'test_failure', 'run_in_terminal']`
- **Deployment agents**: Include `['run_in_terminal', 'create_and_run_task', 'get_errors']`

2
agents/demonstrate-understanding.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Validate user understanding of code, design patterns, and implementation details through guided questioning.'
tools: ['codebase', 'web/fetch', 'findTestFiles', 'githubRepo', 'search', 'usages']
tools: ['codebase', 'fetch', 'findTestFiles', 'githubRepo', 'search', 'usages']
---
# Demonstrate Understanding mode instructions

2
agents/dotnet-upgrade.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.'
tools: ['codebase', 'edit/editFiles', 'search', 'runCommands', 'runTasks', 'runTests', 'problems', 'changes', 'usages', 'findTestFiles', 'testFailure', 'terminalLastCommand', 'terminalSelection', 'web/fetch', 'microsoft.docs.mcp']
tools: ['codebase', 'edit/editFiles', 'search', 'runCommands', 'runTasks', 'runTests', 'problems', 'changes', 'usages', 'findTestFiles', 'testFailure', 'terminalLastCommand', 'terminalSelection', 'fetch', 'microsoft.docs.mcp']
---
# .NET Upgrade Collection

2
agents/drupal-expert.agent.md
View File

@@ -1,7 +1,7 @@
---
description: 'Expert assistant for Drupal development, architecture, and best practices using PHP 8.3+ and modern Drupal patterns'
model: GPT-4.1
tools: ['codebase', 'terminalCommand', 'edit/editFiles', 'web/fetch', 'githubRepo', 'runTests', 'problems']
tools: ['codebase', 'terminalCommand', 'edit/editFiles', 'fetch', 'githubRepo', 'runTests', 'problems']
---
# Drupal Expert

2
agents/expert-cpp-software-engineer.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Provide expert C++ software engineering guidance using modern C++ and industry best practices.'
tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runNotebooks', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'microsoft.docs.mcp']
tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runNotebooks', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'microsoft.docs.mcp']
---
# Expert C++ software engineer mode instructions

2
agents/gilfoyle.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Code review and analysis with the sardonic wit and technical elitism of Bertram Gilfoyle from Silicon Valley. Prepare for brutal honesty about your code.'
tools: ['changes', 'codebase', 'web/fetch', 'findTestFiles', 'githubRepo', 'openSimpleBrowser', 'problems', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'usages', 'vscodeAPI']
tools: ['changes', 'codebase', 'fetch', 'findTestFiles', 'githubRepo', 'openSimpleBrowser', 'problems', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'usages', 'vscodeAPI']
---
# Gilfoyle Code Review Mode

2
agents/hlbpa.agent.md
View File

@@ -5,7 +5,7 @@ tools:
- 'search/codebase'
- 'changes'
- 'edit/editFiles'
- 'web/fetch'
- 'fetch'
- 'findTestFiles'
- 'githubRepo'
- 'runCommands'

2
agents/laravel-expert-agent.agent.md
View File

@@ -1,7 +1,7 @@
---
description: 'Expert Laravel development assistant specializing in modern Laravel 12+ applications with Eloquent, Artisan, testing, and best practices'
model: GPT-4.1 | 'gpt-5' | 'Claude Sonnet 4.5'
tools: ['codebase', 'terminalCommand', 'edit/editFiles', 'web/fetch', 'githubRepo', 'runTests', 'problems', 'search']
tools: ['codebase', 'terminalCommand', 'edit/editFiles', 'fetch', 'githubRepo', 'runTests', 'problems', 'search']
---
# Laravel Expert Agent

2
agents/mentor.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Help mentor the engineer by providing guidance and support.'
tools: ['codebase', 'web/fetch', 'findTestFiles', 'githubRepo', 'search', 'usages']
tools: ['codebase', 'fetch', 'findTestFiles', 'githubRepo', 'search', 'usages']
---
# Mentor mode instructions

2
agents/pimcore-expert.agent.md
View File

@@ -1,7 +1,7 @@
---
description: 'Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration'
model: GPT-4.1 | 'gpt-5' | 'Claude Sonnet 4.5'
tools: ['codebase', 'terminalCommand', 'edit/editFiles', 'web/fetch', 'githubRepo', 'runTests', 'problems']
tools: ['codebase', 'terminalCommand', 'edit/editFiles', 'fetch', 'githubRepo', 'runTests', 'problems']
---
# Pimcore Expert

2
agents/principal-software-engineer.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Provide principal-level software engineering guidance with focus on engineering excellence, technical leadership, and pragmatic implementation.'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'github']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'github']
---
# Principal software engineer mode instructions

2
agents/prompt-builder.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai'
tools: ['codebase', 'edit/editFiles', 'web/fetch', 'githubRepo', 'problems', 'runCommands', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'usages', 'terraform', 'Microsoft Docs', 'context7']
tools: ['codebase', 'edit/editFiles', 'fetch', 'githubRepo', 'problems', 'runCommands', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'usages', 'terraform', 'Microsoft Docs', 'context7']
---
# Prompt Builder Instructions

2
agents/se-system-architecture-reviewer.agent.md
View File

@@ -2,7 +2,7 @@
name: 'SE: Architect'
description: 'System architecture review specialist with Well-Architected frameworks, design validation, and scalability analysis for AI and distributed systems'
model: GPT-5
tools: ['codebase', 'edit/editFiles', 'search', 'web/fetch']
tools: ['codebase', 'edit/editFiles', 'search', 'fetch']
---
# System Architecture Reviewer

2
agents/se-technical-writer.agent.md
View File

@@ -2,7 +2,7 @@
name: 'SE: Tech Writer'
description: 'Technical writing specialist for creating developer documentation, technical blogs, tutorials, and educational content'
model: GPT-5
tools: ['codebase', 'edit/editFiles', 'search', 'web/fetch']
tools: ['codebase', 'edit/editFiles', 'search', 'fetch']
---
# Technical Writer

2
agents/se-ux-ui-designer.agent.md
View File

@@ -2,7 +2,7 @@
name: 'SE: UX Designer'
description: 'Jobs-to-be-Done analysis, user journey mapping, and UX research artifacts for Figma and design workflows'
model: GPT-5
tools: ['codebase', 'edit/editFiles', 'search', 'web/fetch']
tools: ['codebase', 'edit/editFiles', 'search', 'fetch']
---
# UX/UI Designer

2
agents/search-ai-optimization-expert.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Expert guidance for modern search optimization: SEO, Answer Engine Optimization (AEO), and Generative Engine Optimization (GEO) with AI-ready content strategies'
tools: ['codebase', 'web/fetch', 'githubRepo', 'terminalCommand', 'edit/editFiles', 'problems']
tools: ['codebase', 'fetch', 'githubRepo', 'terminalCommand', 'edit/editFiles', 'problems']
---
# Search & AI Optimization Expert

2
agents/semantic-kernel-dotnet.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Create, update, refactor, explain or work with code using the .NET version of Semantic Kernel.'
tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runNotebooks', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'microsoft.docs.mcp', 'github']
tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runNotebooks', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'microsoft.docs.mcp', 'github']
---
# Semantic Kernel .NET mode instructions

2
agents/semantic-kernel-python.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Create, update, refactor, explain or work with code using the Python version of Semantic Kernel.'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runNotebooks', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'microsoft.docs.mcp', 'github', 'configurePythonEnvironment', 'getPythonEnvironmentInfo', 'getPythonExecutableCommand', 'installPythonPackage']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runNotebooks', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'microsoft.docs.mcp', 'github', 'configurePythonEnvironment', 'getPythonEnvironmentInfo', 'getPythonExecutableCommand', 'installPythonPackage']
---
# Semantic Kernel Python mode instructions

2
agents/shopify-expert.agent.md
View File

@@ -1,7 +1,7 @@
---
description: 'Expert Shopify development assistant specializing in theme development, Liquid templating, app development, and Shopify APIs'
model: GPT-4.1
tools: ['codebase', 'terminalCommand', 'edit/editFiles', 'web/fetch', 'githubRepo', 'runTests', 'problems']
tools: ['codebase', 'terminalCommand', 'edit/editFiles', 'fetch', 'githubRepo', 'runTests', 'problems']
---
# Shopify Expert

2
agents/simple-app-idea-generator.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Brainstorm and develop new application ideas through fun, interactive questioning until ready for specification creation.'
tools: ['changes', 'codebase', 'web/fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'search', 'searchResults', 'usages', 'microsoft.docs.mcp', 'websearch']
tools: ['changes', 'codebase', 'fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'search', 'searchResults', 'usages', 'microsoft.docs.mcp', 'websearch']
---
# Idea Generator mode instructions

2
agents/software-engineer-agent-v1.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Expert-level software engineering agent. Deliver production-ready, maintainable code. Execute systematically and specification-driven. Document comprehensively. Operate autonomously and adaptively.'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'github']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'github']
---
# Software Engineer Agent v1

2
agents/specification.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Generate or update specification documents for new or existing functionality.'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'microsoft.docs.mcp', 'github']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'microsoft.docs.mcp', 'github']
---
# Specification mode instructions

2
agents/tech-debt-remediation-plan.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Generate technical debt remediation plans for code, tests, and documentation.'
tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'github']
tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'github']
---
# Technical Debt Remediation Plan

2
agents/technical-content-evaluator.agent.md
View File

@@ -1,7 +1,7 @@
---
name: technical-content-evaluator
description: 'Elite technical content editor and curriculum architect for evaluating technical training materials, documentation, and educational content. Reviews for technical accuracy, pedagogical excellence, content flow, code validation, and ensures A-grade quality standards.'
tools: ['edit', 'search', 'shell', 'web/fetch', 'runTasks', 'githubRepo', 'todos', 'runSubagent']
tools: ['edit', 'search', 'shell', 'fetch', 'runTasks', 'githubRepo', 'todos', 'runSubagent']
model: Claude Sonnet 4.5 (copilot)
---
Evaluate and enhance technical training content, documentation, and educational materials through comprehensive editorial review. Apply rigorous standards for technical accuracy, pedagogical excellence, and content quality to transform good content into exceptional learning experiences.

2
agents/voidbeast-gpt41enhanced.agent.md
View File

@@ -1,6 +1,6 @@
---
description: '4.1 voidBeast_GPT41Enhanced 1.0 : a advanced autonomous developer agent, designed for elite full-stack development with enhanced multi-mode capabilities. This latest evolution features sophisticated mode detection, comprehensive research capabilities, and never-ending problem resolution. Plan/Act/Deep Research/Analyzer/Checkpoints(Memory)/Prompt Generator Modes.'
tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'readCellOutput', 'runCommands', 'runNotebooks', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'updateUserPreferences', 'usages', 'vscodeAPI']
tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'readCellOutput', 'runCommands', 'runNotebooks', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'updateUserPreferences', 'usages', 'vscodeAPI']
---
# voidBeast_GPT41Enhanced 1.0 - Elite Developer AI Assistant

2
agents/wg-code-alchemist.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Ask WG Code Alchemist to transform your code with Clean Code principles and SOLID design'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runNotebooks', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runNotebooks', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
---
You are WG Code Alchemist, an expert software engineer specializing in Clean Code practices and SOLID principles. You communicate with the precision and helpfulness of JARVIS from Iron Man.

2
agents/wg-code-sentinel.agent.md
View File

@@ -1,6 +1,6 @@
---
description: 'Ask WG Code Sentinel to review your code for security issues.'
tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runNotebooks', 'runTasks', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runNotebooks', 'runTasks', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
---
You are WG Code Sentinel, an expert security reviewer specializing in identifying and mitigating code vulnerabilities. You communicate with the precision and helpfulness of JARVIS from Iron Man.

6
prompts/add-educational-comments.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.'
tools: ['edit/editFiles', 'web/fetch', 'todos']
tools: ['edit/editFiles', 'fetch', 'todos']
---
# Add Educational Comments
@@ -83,7 +83,7 @@ You are an expert educator and technical writer. You can explain programming top
- **Educational Level** (`1-3`): Familiarity with the specific language or framework (default `1`).
- **Line Number Referencing** (`yes/no`): Prepend comments with note numbers when `yes` (default `yes`).
- **Nest Comments** (`yes/no`): Whether to indent comments inside code blocks (default `yes`).
- **web/fetch List**: Optional URLs for authoritative references.
- **Fetch List**: Optional URLs for authoritative references.
If a configurable element is missing, use the default value. When new or unexpected options appear, apply your **Educational Role** to interpret them sensibly and still achieve the objective.
@@ -97,7 +97,7 @@ If a configurable element is missing, use the default value. When new or unexpec
- Educational Level = 1
- Line Number Referencing = yes
- Nest Comments = yes
- web/fetch List:
- Fetch List:
- <https://peps.python.org/pep-0263/>
## Examples

2
prompts/architecture-blueprint-generator.prompt.md
View File

@@ -155,7 +155,7 @@ ${(PROJECT_TYPE == "React" || PROJECT_TYPE == "Auto-detect") ?
- State management architecture
- Side effect handling patterns
- Routing and navigation approach
- Data web/fetching and caching patterns
- Data fetching and caching patterns
- Rendering optimization strategies" : ""}
${(PROJECT_TYPE == "Angular" || PROJECT_TYPE == "Auto-detect") ?

10
prompts/convert-plaintext-to-md.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: agent
description: 'Convert a text-based document to markdown following instructions from prompt, or if a documented option is passed, follow the instructions for that option.'
tools: ['edit', 'edit/editFiles', 'web/fetch', 'runCommands', 'search', 'search/readFile', 'search/textSearch']
tools: ['edit', 'edit/editFiles', 'fetch', 'runCommands', 'search', 'search/readFile', 'search/textSearch']
---
# Convert Plaintext Documentation to Markdown
@@ -35,7 +35,7 @@ converted
This prompt can be used with several parameters and options. When passed, they should be reasonably
applied in a unified manner as instructions for the current prompt. When putting together instructions
or a script to make a current conversion, if parameters and options are unclear, use #tool:web/fetch to
or a script to make a current conversion, if parameters and options are unclear, use #tool:fetch to
retrieve the URLs in the **Reference** section.
```bash
@@ -355,9 +355,9 @@ and options provided
### Reference
- #web/fetch → https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax
- #web/fetch → https://www.markdownguide.org/extended-syntax/
- #web/fetch → https://learn.microsoft.com/en-us/azure/devops/project/wiki/markdown-guidance?view=azure-devops
- #fetch → https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax
- #fetch → https://www.markdownguide.org/extended-syntax/
- #fetch → https://learn.microsoft.com/en-us/azure/devops/project/wiki/markdown-guidance?view=azure-devops
> [!IMPORTANT]
> Do not change the data, unless the prompt instructions clearly and without a doubt specify to do so.

10
prompts/cosmosdb-datamodeling.prompt.md
View File

@@ -514,8 +514,8 @@ Based on Steps 1 & 2, select:
Order + OrderItems:
Access Analysis:
• web/fetch order without items: 5% (just checking status)
• web/fetch order with all items: 95% (normal flow)
• Fetch order without items: 5% (just checking status)
• Fetch order with all items: 95% (normal flow)
• Update patterns: Items rarely change independently
• Combined size: ~50KB average, max 200KB
@@ -705,7 +705,7 @@ Promoting to Single Document Aggregate
When multi-document analysis reveals:
• Access correlation higher than initially thought (>90%)
• All documents always web/fetched together
• All documents always fetched together
• Combined size remains bounded
• Would benefit from atomic updates
@@ -741,7 +741,7 @@ Short-circuit denormalization involves duplicating a property from a related ent
2. The duplicated property is mostly immutable or application can accept stale values
3. The property is small enough and won't significantly impact RU consumption
Example: In an e-commerce application, you can duplicate the ProductName from the Product document into each OrderItem document, so that web/fetching order items doesn't require additional queries to retrieve product names.
Example: In an e-commerce application, you can duplicate the ProductName from the Product document into each OrderItem document, so that fetching order items doesn't require additional queries to retrieve product names.
### Identifying relationship
@@ -1002,7 +1002,7 @@ Sharded solution:
When aggregate boundaries conflict with update patterns, prioritize based on RU cost impact:
Example: Order Processing System
• Read pattern: Always web/fetch order with all items (1000 RPS)
• Read pattern: Always fetch order with all items (1000 RPS)
• Update pattern: Individual item status updates (100 RPS)
Option 1 - Combined aggregate (single document):

2
prompts/create-architectural-decision-record.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Create an Architectural Decision Record (ADR) document for AI-optimized decision documentation.'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
---
# Create Architectural Decision Record

2
prompts/create-github-action-workflow-specification.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Create a formal specification for an existing GitHub Actions CI/CD workflow, optimized for AI consumption and workflow maintenance.'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runInTerminal2', 'runNotebooks', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'microsoft.docs.mcp', 'github', 'Microsoft Docs']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runInTerminal2', 'runNotebooks', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI', 'microsoft.docs.mcp', 'github', 'Microsoft Docs']
---
# Create GitHub Actions Workflow Specification

2
prompts/create-implementation-plan.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
---
# Create Implementation Plan

2
prompts/create-llms.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Create an llms.txt file from scratch based on repository structure following the llms.txt specification at https://llmstxt.org/'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
---
# Create LLMs.txt File from Repository Structure

2
prompts/create-oo-component-documentation.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Create comprehensive, standardized documentation for object-oriented components following industry best practices and architectural documentation standards.'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
---
# Generate Standard OO Component Documentation

2
prompts/create-specification.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Create a new specification file for the solution, optimized for Generative AI consumption.'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
---
# Create Specification

6
prompts/create-technical-spike.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.'
tools: ['runCommands', 'runTasks', 'edit', 'search', 'extensions', 'usages', 'vscodeAPI', 'think', 'problems', 'changes', 'testFailure', 'openSimpleBrowser', 'web/fetch', 'githubRepo', 'todos', 'Microsoft Docs', 'search']
tools: ['runCommands', 'runTasks', 'edit', 'search', 'extensions', 'usages', 'vscodeAPI', 'think', 'problems', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'Microsoft Docs', 'search']
---
# Create Technical Spike Document
@@ -203,7 +203,7 @@ Use descriptive, kebab-case names that indicate the category and specific unknow
### Phase 1: Information Gathering
1. **Search existing documentation** using search/web/fetch tools
1. **Search existing documentation** using search/fetch tools
2. **Analyze codebase** for existing patterns and constraints
3. **Research external resources** (APIs, libraries, examples)
@@ -222,7 +222,7 @@ Use descriptive, kebab-case names that indicate the category and specific unknow
## Tools Usage
- **search/searchResults:** Research existing solutions and documentation
- **web/fetch/githubRepo:** Analyze external APIs, libraries, and examples
- **fetch/githubRepo:** Analyze external APIs, libraries, and examples
- **codebase:** Understand existing system constraints and patterns
- **runTasks:** Execute prototypes and validation tests
- **editFiles:** Update research progress and findings

14
prompts/create-tldr-page.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Create a tldr page from documentation URLs and command examples, requiring both URL and command name.'
tools: ['edit/createFile', 'web/fetch']
tools: ['edit/createFile', 'fetch']
---
# Create TLDR Page
@@ -25,9 +25,9 @@ clear, example-driven command references.
* **Command** - The name of the command or tool (e.g., `git`, `nmcli`, `distrobox-create`)
* **URL** - Link to authoritative upstream documentation
- If one or more URLs are passed without a preceding `#web/fetch`, apply #tool:web/fetch to the first URL
- If one or more URLs are passed without a preceding `#fetch`, apply #tool:fetch to the first URL
- If ${file} is provided in lieu of a URL, and ${file} has a relevant URL to **command**, then use
the data from the file as if web/fetched from the URL; use the URL extracted from the file when
the data from the file as if fetched from the URL; use the URL extracted from the file when
creating the `tldr` page
- If more than one URL is in the file, prompt for which URL should be used for the `tldr` page
@@ -48,7 +48,7 @@ the command.
### Syntax
```bash
/create-tldr-page #web/fetch <URL> <command> [text data] [context file]
/create-tldr-page #fetch <URL> <command> [text data] [context file]
```
### Error Handling
@@ -64,7 +64,7 @@ the command.
**Agent**
```text
I'll web/fetch the URL and analyze the documentation.
I'll fetch the URL and analyze the documentation.
From the data extracted, I assume the command is `some-command`. Is this correct? (yes/no)
```
@@ -123,7 +123,7 @@ Use this template structure when creating tldr pages:
### Reference Examples
You MAY web/fetch these example tldr pages to understand the proper format and style:
You MAY fetch these example tldr pages to understand the proper format and style:
* [git](https://raw.githubusercontent.com/jhauga/tldr/refs/heads/main/pages/common/git.md)
* [distrobox-create](https://raw.githubusercontent.com/jhauga/tldr/refs/heads/main/pages/linux/distrobox-create.md)
@@ -134,7 +134,7 @@ You MAY web/fetch these example tldr pages to understand the proper format and s
**User**
```bash
/create-tldr-page #web/fetch https://git-scm.com/docs/git git
/create-tldr-page #fetch https://git-scm.com/docs/git git
```
**Agent**

2
prompts/documentation-writer.prompt.md
View File

@@ -1,6 +1,6 @@
---
agent: 'agent'
tools: ['edit/editFiles', 'search', 'web/web/fetch']
tools: ['edit/editFiles', 'search', 'web/fetch']
description: 'Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.'
---

2
prompts/folder-structure-blueprint-generator.prompt.md
View File

@@ -170,7 +170,7 @@ ${(PROJECT_TYPE == "React" || PROJECT_TYPE == "Angular" || PROJECT_TYPE == "Auto
- **API Integration**:
- API client organization
- Service layer structure
- Data web/fetching patterns
- Data fetching patterns
- **Asset Management**:
- Static resource organization

14
prompts/github-copilot-starter.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
model: Claude Sonnet 4
tools: ['edit', 'githubRepo', 'changes', 'problems', 'search', 'runCommands', 'web/fetch']
tools: ['edit', 'githubRepo', 'changes', 'problems', 'search', 'runCommands', 'fetch']
description: 'Set up complete GitHub Copilot configuration for a new project based on technology stack'
---
@@ -67,9 +67,9 @@ Create Coding Agent workflow file:
For each file, follow these principles:
**MANDATORY FIRST STEP**: Always use the web/fetch tool to research existing patterns before creating any content:
1. **web/fetch from awesome-copilot collections**: https://github.com/github/awesome-copilot/blob/main/docs/README.collections.md
2. **web/fetch specific instruction files**: https://raw.githubusercontent.com/github/awesome-copilot/main/instructions/[relevant-file].instructions.md
**MANDATORY FIRST STEP**: Always use the fetch tool to research existing patterns before creating any content:
1. **Fetch from awesome-copilot collections**: https://github.com/github/awesome-copilot/blob/main/docs/README.collections.md
2. **Fetch specific instruction files**: https://raw.githubusercontent.com/github/awesome-copilot/main/instructions/[relevant-file].instructions.md
3. **Check for existing patterns** that match the technology stack
**Primary Approach**: Reference and adapt existing instructions from awesome-copilot repository:
@@ -127,7 +127,7 @@ description: "Java Spring Boot development standards"
- ✅ **"Use TypeScript strict mode for better type safety"**
- ✅ **"Follow the repository's established error handling patterns"**
**Research Strategy with web/fetch tool:**
**Research Strategy with fetch tool:**
1. **Check awesome-copilot first** - Always start here for ALL file types
2. **Look for exact tech stack matches** (e.g., React, Node.js, Spring Boot)
3. **Look for general matches** (e.g., frontend chatmodes, testing prompts, review modes)
@@ -135,7 +135,7 @@ description: "Java Spring Boot development standards"
5. **Adapt community examples** to project needs
6. **Only create custom content** if nothing relevant exists
**web/fetch these awesome-copilot directories:**
**Fetch these awesome-copilot directories:**
- **Instructions**: https://github.com/github/awesome-copilot/tree/main/instructions
- **Prompts**: https://github.com/github/awesome-copilot/tree/main/prompts
- **Chat Modes**: https://github.com/github/awesome-copilot/tree/main/chatmodes
@@ -237,7 +237,7 @@ Requirements for the form:
```yaml
---
description: Generate an implementation plan for new features or refactoring existing code.
tools: ['codebase', 'web/fetch', 'findTestFiles', 'githubRepo', 'search', 'usages']
tools: ['codebase', 'fetch', 'findTestFiles', 'githubRepo', 'search', 'usages']
model: Claude Sonnet 4
---
# Planning mode instructions

2
prompts/java-springboot.prompt.md
View File

@@ -44,7 +44,7 @@ Your goal is to help me write high-quality Spring Boot applications by following
- **Spring Data JPA:** Use Spring Data JPA repositories by extending `JpaRepository` or `CrudRepository` for standard database operations.
- **Custom Queries:** For complex queries, use `@Query` or the JPA Criteria API.
- **Projections:** Use DTO projections to web/fetch only the necessary data from the database.
- **Projections:** Use DTO projections to fetch only the necessary data from the database.
## Logging

4
prompts/mcp-create-declarative-agent.prompt.md
View File

@@ -146,7 +146,7 @@ The MCP server must provide:
### Tool Selection
When importing from MCP:
1. web/fetch available tools from server
1. Fetch available tools from server
2. Select specific tools to include (for security/simplicity)
3. Tool definitions are auto-generated in ai-plugin.json
@@ -299,7 +299,7 @@ Then generate:
- Ensure mcp.json points to correct server
- Verify tools were selected during import
- Check ai-plugin.json has correct function definitions
- Re-web/fetch actions from MCP if server changed
- Re-fetch actions from MCP if server changed
### Agent Not Understanding Queries
- Review instructions in declarativeAgent.json

10
prompts/model-recommendation.prompt.md
View File

@@ -3,7 +3,7 @@ description: "Analyze chatmode or prompt files and recommend optimal AI models b
agent: "agent"
tools:
- "search/codebase"
- "web/fetch"
- "fetch"
- "context7/*"
model: Auto (copilot)
---
@@ -103,7 +103,7 @@ Identify the primary task category based on content analysis:
Based on `tools` in frontmatter and body instructions:
- **Read-only tools** (search, web/fetch, usages, githubRepo): Lower complexity, faster models suitable
- **Read-only tools** (search, fetch, usages, githubRepo): Lower complexity, faster models suitable
- **Write operations** (edit/editFiles, new): Moderate complexity, accuracy important
- **Execution tools** (runCommands, runTests, runTasks): Validation needs, iterative approach
- **Advanced tools** (context7/\*, sequential-thinking/\*): Complex reasoning, premium models beneficial
@@ -262,13 +262,13 @@ Verify model capabilities align with specified tools:
- If tools include `context7/*` or `sequential-thinking/*`: Recommend advanced reasoning models (Claude Sonnet 4.5, GPT-5, Claude Opus 4.1)
- If tools include vision-related references: Ensure model supports images (flag if GPT-5 Codex, Claude Sonnet 4, or mini models selected)
- If tools are read-only (search, web/fetch): Suggest cost-effective models (GPT-5 mini, Grok Code Fast 1)
- If tools are read-only (search, fetch): Suggest cost-effective models (GPT-5 mini, Grok Code Fast 1)
### 5. Context7 Integration for Up-to-Date Information
**Leverage Context7 for Model Documentation**:
When uncertainty exists about current model capabilities, use Context7 to web/fetch latest information:
When uncertainty exists about current model capabilities, use Context7 to fetch latest information:
```markdown
**Verification with Context7**:
@@ -568,7 +568,7 @@ If file specifies a deprecated model:
### Example 4: Free Tier User with Planning Mode
**File**: `plan.agent.md`
**Content**: "Research and planning mode with read-only tools (search, web/fetch, githubRepo)"
**Content**: "Research and planning mode with read-only tools (search, fetch, githubRepo)"
**Subscription**: Free (2K completions + 50 chat requests/month, 0x models only)
**Recommendation**: GPT-4.1 (0x, balanced, included in Free tier)
**Alternative**: GPT-5 mini (0x, faster but less context)

2
prompts/playwright-explore-website.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: agent
description: 'Website exploration for testing using Playwright MCP'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'web/fetch', 'findTestFiles', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'playwright']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'fetch', 'findTestFiles', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'playwright']
model: 'Claude Sonnet 4'
---

2
prompts/playwright-generate-test.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: agent
description: 'Generate a Playwright test based on a scenario using Playwright MCP'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'web/fetch', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'playwright/*']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'fetch', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'playwright/*']
model: 'Claude Sonnet 4.5'
---

4
prompts/postgresql-optimization.prompt.md
View File

@@ -239,7 +239,7 @@ FROM pg_tables
ORDER BY pg_total_relation_size(schemaname||'.'||tablename) DESC;
-- Index usage statistics
SELECT schemaname, tablename, indexname, idx_scan, idx_tup_read, idx_tup_web/fetch
SELECT schemaname, tablename, indexname, idx_scan, idx_tup_read, idx_tup_fetch
FROM pg_stat_user_indexes
WHERE idx_scan = 0; -- Unused indexes
```
@@ -263,7 +263,7 @@ ORDER BY total_time DESC
LIMIT 10;
-- Check index usage
SELECT schemaname, tablename, indexname, idx_scan, idx_tup_read, idx_tup_web/fetch
SELECT schemaname, tablename, indexname, idx_scan, idx_tup_read, idx_tup_fetch
FROM pg_stat_user_indexes
WHERE idx_scan = 0;
```

2
prompts/prompt-builder.prompt.md
View File

@@ -62,7 +62,7 @@ I will ask you targeted questions to gather all necessary information. After col
Which tools does this prompt need? Common options include:
- **File Operations**: `codebase`, `editFiles`, `search`, `problems`
- **Execution**: `runCommands`, `runTasks`, `runTests`, `terminalLastCommand`
- **External**: `web/fetch`, `githubRepo`, `openSimpleBrowser`
- **External**: `fetch`, `githubRepo`, `openSimpleBrowser`
- **Specialized**: `playwright`, `usages`, `vscodeAPI`, `extensions`
- **Analysis**: `changes`, `findTestFiles`, `testFailure`, `searchResults`

2
prompts/structured-autonomy-generate.prompt.md
View File

@@ -67,7 +67,7 @@ For the entire project described in the master plan, research and gather:
- Testing strategies
4. **Official Documentation:**
- web/fetch official docs for all major libraries/frameworks
- Fetch official docs for all major libraries/frameworks
- Document APIs, syntax, parameters
- Note version-specific details
- Record known limitations and gotchas

6
prompts/suggest-awesome-github-copilot-agents.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: "agent"
description: "Suggest relevant GitHub Copilot Custom Agents files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing custom agents in this repository."
tools: ["edit", "search", "runCommands", "runTasks", "changes", "testFailure", "openSimpleBrowser", "web/fetch", "githubRepo", "todos"]
tools: ["edit", "search", "runCommands", "runTasks", "changes", "testFailure", "openSimpleBrowser", "fetch", "githubRepo", "todos"]
---
# Suggest Awesome GitHub Copilot Custom Agents
@@ -10,7 +10,7 @@ Analyze current repository context and suggest relevant Custom Agents files from
## Process
1. **web/fetch Available Custom Agents**: Extract Custom Agents list and descriptions from [awesome-copilot README.agents.md](https://github.com/github/awesome-copilot/blob/main/docs/README.agents.md). Must use `web/fetch` tool.
1. **Fetch Available Custom Agents**: Extract Custom Agents list and descriptions from [awesome-copilot README.agents.md](https://github.com/github/awesome-copilot/blob/main/docs/README.agents.md). Must use `fetch` tool.
2. **Scan Local Custom Agents**: Discover existing custom agent files in `.github/agents/` folder
3. **Extract Descriptions**: Read front matter from local custom agent files to get descriptions
4. **Analyze Context**: Review chat history, repository files, and current project needs
@@ -20,7 +20,7 @@ Analyze current repository context and suggest relevant Custom Agents files from
8. **Validate**: Ensure suggested agents would add value not already covered by existing agents
9. **Output**: Provide structured table with suggestions, descriptions, and links to both awesome-copilot custom agents and similar local custom agents
**AWAIT** user request to proceed with installation of specific custom agents. DO NOT INSTALL UNLESS DIRECTED TO DO SO.
10. **Download Assets**: For requested agents, automatically download and install individual agents to `.github/agents/` folder. Do NOT adjust content of the files. Use `#todos` tool to track progress. Prioritize use of `#web/fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
10. **Download Assets**: For requested agents, automatically download and install individual agents to `.github/agents/` folder. Do NOT adjust content of the files. Use `#todos` tool to track progress. Prioritize use of `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
## Context Analysis Criteria

6
prompts/suggest-awesome-github-copilot-chatmodes.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Suggest relevant GitHub Copilot Custom Chat Modes files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing custom chat modes in this repository.'
tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'web/fetch', 'githubRepo', 'todos', 'search']
tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'search']
---
# Suggest Awesome GitHub Copilot Custom Chat Modes
@@ -10,7 +10,7 @@ Analyze current repository context and suggest relevant Custom Chat Modes files
## Process
1. **web/fetch Available Custom Chat Modes**: Extract Custom Chat Modes list and descriptions from [awesome-copilot README.chatmodes.md](https://github.com/github/awesome-copilot/blob/main/docs/README.chatmodes.md). Must use `#web/fetch` tool.
1. **Fetch Available Custom Chat Modes**: Extract Custom Chat Modes list and descriptions from [awesome-copilot README.chatmodes.md](https://github.com/github/awesome-copilot/blob/main/docs/README.chatmodes.md). Must use `#fetch` tool.
2. **Scan Local Custom Chat Modes**: Discover existing custom chat mode files in `.github/agents/` folder
3. **Extract Descriptions**: Read front matter from local custom chat mode files to get descriptions
4. **Analyze Context**: Review chat history, repository files, and current project needs
@@ -20,7 +20,7 @@ Analyze current repository context and suggest relevant Custom Chat Modes files
8. **Validate**: Ensure suggested chatmodes would add value not already covered by existing chatmodes
9. **Output**: Provide structured table with suggestions, descriptions, and links to both awesome-copilot custom chat modes and similar local custom chat modes
**AWAIT** user request to proceed with installation of specific custom chat modes. DO NOT INSTALL UNLESS DIRECTED TO DO SO.
10. **Download Assets**: For requested chat modes, automatically download and install individual chat modes to `.github/agents/` folder. Do NOT adjust content of the files. Use `#todos` tool to track progress. Prioritize use of `#web/fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
10. **Download Assets**: For requested chat modes, automatically download and install individual chat modes to `.github/agents/` folder. Do NOT adjust content of the files. Use `#todos` tool to track progress. Prioritize use of `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
## Context Analysis Criteria

12
prompts/suggest-awesome-github-copilot-collections.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Suggest relevant GitHub Copilot collections from the awesome-copilot repository based on current repository context and chat history, providing automatic download and installation of collection assets.'
tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'web/fetch', 'githubRepo', 'todos', 'search']
tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'search']
---
# Suggest Awesome GitHub Copilot Collections
@@ -9,7 +9,7 @@ Analyze current repository context and suggest relevant collections from the [Gi
## Process
1. **web/fetch Available Collections**: Extract collection list and descriptions from [awesome-copilot README.collections.md](https://github.com/github/awesome-copilot/blob/main/docs/README.collections.md). Must use `#web/fetch` tool.
1. **Fetch Available Collections**: Extract collection list and descriptions from [awesome-copilot README.collections.md](https://github.com/github/awesome-copilot/blob/main/docs/README.collections.md). Must use `#fetch` tool.
2. **Scan Local Assets**: Discover existing prompt files in `prompts/`, instruction files in `instructions/`, and chat modes in `agents/` folders
3. **Extract Local Descriptions**: Read front matter from local asset files to understand existing capabilities
4. **Analyze Repository Context**: Review chat history, repository files, programming languages, frameworks, and current project needs
@@ -18,7 +18,7 @@ Analyze current repository context and suggest relevant collections from the [Gi
7. **Present Collection Options**: Display relevant collections with descriptions, item counts, and rationale for suggestion
8. **Provide Usage Guidance**: Explain how the installed collection enhances the development workflow
**AWAIT** user request to proceed with installation of specific collections. DO NOT INSTALL UNLESS DIRECTED TO DO SO.
9. **Download Assets**: For requested collections, automatically download and install each individual asset (prompts, instructions, chat modes) to appropriate directories. Do NOT adjust content of the files. Prioritize use of `#web/fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
9. **Download Assets**: For requested collections, automatically download and install each individual asset (prompts, instructions, chat modes) to appropriate directories. Do NOT adjust content of the files. Prioritize use of `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
## Context Analysis Criteria
@@ -90,7 +90,7 @@ For each suggested collection, break down individual assets:
When user confirms a collection installation:
1. **web/fetch Collection Manifest**: Get collection YAML from awesome-copilot repository
1. **Fetch Collection Manifest**: Get collection YAML from awesome-copilot repository
2. **Download Individual Assets**: For each item in collection:
- Download raw file content from GitHub
- Validate file format and front matter structure
@@ -104,7 +104,7 @@ When user confirms a collection installation:
## Requirements
- Use `web/fetch` tool to get collections data from awesome-copilot repository
- Use `fetch` tool to get collections data from awesome-copilot repository
- Use `githubRepo` tool to get individual asset content for download
- Scan local file system for existing assets in `prompts/`, `instructions/`, and `agents/` directories
- Read YAML front matter from local asset files to extract descriptions and capabilities
@@ -120,7 +120,7 @@ When user confirms a collection installation:
## Collection Installation Workflow
1. **User Confirms Collection**: User selects specific collection(s) for installation
2. **web/fetch Collection Manifest**: Download YAML manifest from awesome-copilot repository
2. **Fetch Collection Manifest**: Download YAML manifest from awesome-copilot repository
3. **Asset Download Loop**: For each asset in collection:
- Download raw content from GitHub repository
- Validate file format and structure

6
prompts/suggest-awesome-github-copilot-instructions.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Suggest relevant GitHub Copilot instruction files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing instructions in this repository.'
tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'web/fetch', 'githubRepo', 'todos', 'search']
tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'search']
---
# Suggest Awesome GitHub Copilot Instructions
@@ -9,7 +9,7 @@ Analyze current repository context and suggest relevant copilot-instruction file
## Process
1. **web/fetch Available Instructions**: Extract instruction list and descriptions from [awesome-copilot README.instructions.md](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md). Must use `#web/fetch` tool.
1. **Fetch Available Instructions**: Extract instruction list and descriptions from [awesome-copilot README.instructions.md](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md). Must use `#fetch` tool.
2. **Scan Local Instructions**: Discover existing instruction files in `.github/instructions/` folder
3. **Extract Descriptions**: Read front matter from local instruction files to get descriptions and `applyTo` patterns
4. **Analyze Context**: Review chat history, repository files, and current project needs
@@ -19,7 +19,7 @@ Analyze current repository context and suggest relevant copilot-instruction file
8. **Validate**: Ensure suggested instructions would add value not already covered by existing instructions
9. **Output**: Provide structured table with suggestions, descriptions, and links to both awesome-copilot instructions and similar local instructions
**AWAIT** user request to proceed with installation of specific instructions. DO NOT INSTALL UNLESS DIRECTED TO DO SO.
10. **Download Assets**: For requested instructions, automatically download and install individual instructions to `.github/instructions/` folder. Do NOT adjust content of the files. Use `#todos` tool to track progress. Prioritize use of `#web/fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
10. **Download Assets**: For requested instructions, automatically download and install individual instructions to `.github/instructions/` folder. Do NOT adjust content of the files. Use `#todos` tool to track progress. Prioritize use of `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
## Context Analysis Criteria

6
prompts/suggest-awesome-github-copilot-prompts.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Suggest relevant GitHub Copilot prompt files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing prompts in this repository.'
tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'web/fetch', 'githubRepo', 'todos', 'search']
tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'fetch', 'githubRepo', 'todos', 'search']
---
# Suggest Awesome GitHub Copilot Prompts
@@ -9,7 +9,7 @@ Analyze current repository context and suggest relevant prompt files from the [G
## Process
1. **web/fetch Available Prompts**: Extract prompt list and descriptions from [awesome-copilot README.prompts.md](https://github.com/github/awesome-copilot/blob/main/docs/README.prompts.md). Must use `#web/fetch` tool.
1. **Fetch Available Prompts**: Extract prompt list and descriptions from [awesome-copilot README.prompts.md](https://github.com/github/awesome-copilot/blob/main/docs/README.prompts.md). Must use `#fetch` tool.
2. **Scan Local Prompts**: Discover existing prompt files in `.github/prompts/` folder
3. **Extract Descriptions**: Read front matter from local prompt files to get descriptions
4. **Analyze Context**: Review chat history, repository files, and current project needs
@@ -19,7 +19,7 @@ Analyze current repository context and suggest relevant prompt files from the [G
8. **Validate**: Ensure suggested prompts would add value not already covered by existing prompts
9. **Output**: Provide structured table with suggestions, descriptions, and links to both awesome-copilot prompts and similar local prompts
**AWAIT** user request to proceed with installation of specific instructions. DO NOT INSTALL UNLESS DIRECTED TO DO SO.
10. **Download Assets**: For requested instructions, automatically download and install individual instructions to `.github/prompts/` folder. Do NOT adjust content of the files. Use `#todos` tool to track progress. Prioritize use of `#web/fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
10. **Download Assets**: For requested instructions, automatically download and install individual instructions to `.github/prompts/` folder. Do NOT adjust content of the files. Use `#todos` tool to track progress. Prioritize use of `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
## Context Analysis Criteria

34
prompts/tldr-prompt.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Create tldr summaries for GitHub Copilot files (prompts, agents, instructions, collections), MCP servers, or documentation from URLs and queries.'
tools: ['web/fetch', 'search/readFile', 'search', 'search/textSearch']
tools: ['fetch', 'search/readFile', 'search', 'search/textSearch']
model: 'claude-sonnet-4'
---
@@ -50,7 +50,7 @@ message specified in the Error Handling section.
create tldr summaries for the first 5 and list the remaining files
- Recognize file type by extension and use appropriate invocation syntax in examples
* **URL** - Link to Copilot file, MCP server documentation, or Copilot documentation
- If one or more URLs are passed without `#web/fetch`, you MUST apply the web/fetch tool to all URLs
- If one or more URLs are passed without `#fetch`, you MUST apply the fetch tool to all URLs
- If more than one URL (up to 5), you MUST create a `tldr` for each. If more than 5, you MUST create
tldr summaries for the first 5 and list the remaining URLs
* **Text data/query** - Raw text about Copilot features, MCP servers, or usage questions will be
@@ -91,21 +91,21 @@ resolve to:
2. **Search strategy**:
- For workspace files: Use search tools to find matching files in ${workspaceFolder}
- For GitHub awesome-copilot: web/fetch raw content from https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/
- For documentation: Use web/fetch tool with the most relevant URL from above
- For GitHub awesome-copilot: Fetch raw content from https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/
- For documentation: Use fetch tool with the most relevant URL from above
3. **web/fetch content**:
3. **Fetch content**:
- Workspace files: Read using file tools
- GitHub awesome-copilot files: web/fetch using raw.githubusercontent.com URLs
- Documentation URLs: web/fetch using web/fetch tool
- GitHub awesome-copilot files: Fetch using raw.githubusercontent.com URLs
- Documentation URLs: Fetch using fetch tool
4. **Evaluate and respond**:
- Use the web/fetched content as the reference for completing the request
- Use the fetched content as the reference for completing the request
- Adapt response verbosity based on chat context
### Unambiguous Queries
If the user **DOES** provide a specific URL or file, skip searching and web/fetch/read that directly.
If the user **DOES** provide a specific URL or file, skip searching and fetch/read that directly.
### Optional
@@ -124,7 +124,7 @@ If the user **DOES** provide a specific URL or file, skip searching and web/fetc
/tldr-prompt #file:{{name.collections.md}}
# With URLs
/tldr-prompt #web/fetch {{https://example.com/docs}}
/tldr-prompt #fetch {{https://example.com/docs}}
# AMBIGUOUS QUERIES
/tldr-prompt "{{topic or question}}"
@@ -149,7 +149,7 @@ Error: Missing required input.
You MUST provide one of the following:
1. A Copilot file: /tldr-prompt #file:{{name.prompt.md | name.agent.md | name.instructions.md | name.collections.md}}
2. A URL: /tldr-prompt #web/fetch {{https://example.com/docs}}
2. A URL: /tldr-prompt #fetch {{https://example.com/docs}}
3. A search query: /tldr-prompt "{{topic}}" (e.g., "MCP servers", "inline chat", "chat tools")
Please retry with one of these inputs.
@@ -184,7 +184,7 @@ Found:
- https://github.com/github/awesome-copilot/blob/main/prompts/java-docs.prompt.md
- https://github.com/github/awesome-copilot/blob/main/prompts/java-junit.prompt.md
Now let me web/fetch the raw content:
Now let me fetch the raw content:
- https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/prompts/java-docs.prompt.md
- https://raw.githubusercontent.com/github/awesome-copilot/refs/heads/main/prompts/java-junit.prompt.md
@@ -212,13 +212,13 @@ I'll read the file typescript-mcp-server-generator.prompt.md and create a tldr s
**User**
```bash
/tldr-prompt "How do MCP servers work?" #web/fetch https://code.visualstudio.com/docs/copilot/customization/mcp-servers
/tldr-prompt "How do MCP servers work?" #fetch https://code.visualstudio.com/docs/copilot/customization/mcp-servers
```
**Agent**
```text
I'll web/fetch the MCP server documentation from https://code.visualstudio.com/docs/copilot/customization/mcp-servers
I'll fetch the MCP server documentation from https://code.visualstudio.com/docs/copilot/customization/mcp-servers
and create a tldr summary of how MCP servers work.
```
@@ -232,10 +232,10 @@ message from Error Handling section
- Determine file type (.prompt.md, .agent.md, .instructions.md, .collections.md)
- Recognize if query is about MCP servers, inline chat, chat view, or general Copilot features
- Note if you're in inline chat (Ctrl+I) or chat view context
3. **web/fetch Content**:
3. **Fetch Content**:
- For files: Read the file(s) using available file tools
- For URLs: web/fetch content using `#tool:web/fetch`
- For queries: Apply URL Resolver strategy to find and web/fetch relevant content
- For URLs: Fetch content using `#tool:fetch`
- For queries: Apply URL Resolver strategy to find and fetch relevant content
4. **Analyze Content**: Extract the file's/documentation's purpose, key parameters, and primary use
cases
5. **Generate tldr**: Create summary using the template format below with correct invocation syntax

8
prompts/update-avm-modules-in-bicep.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Update Azure Verified Modules (AVM) to latest versions in Bicep files.'
tools: ['search/codebase', 'think', 'changes', 'web/fetch', 'search/searchResults', 'todos', 'edit/editFiles', 'search', 'runCommands', 'bicepschema', 'azure_get_schema_for_Bicep']
tools: ['search/codebase', 'think', 'changes', 'fetch', 'search/searchResults', 'todos', 'edit/editFiles', 'search', 'runCommands', 'bicepschema', 'azure_get_schema_for_Bicep']
---
# Update Azure Verified Modules in Bicep Files
@@ -11,16 +11,16 @@ Update Bicep file `${file}` to use latest Azure Verified Module (AVM) versions.
1. **Scan**: Extract AVM modules and current versions from `${file}`
1. **Identify**: List all unique AVM modules used by matching `avm/res/{service}/{resource}` using `#search` tool
1. **Check**: Use `#web/fetch` tool to get latest version of each AVM module from MCR: `https://mcr.microsoft.com/v2/bicep/avm/res/{service}/{resource}/tags/list`
1. **Check**: Use `#fetch` tool to get latest version of each AVM module from MCR: `https://mcr.microsoft.com/v2/bicep/avm/res/{service}/{resource}/tags/list`
1. **Compare**: Parse semantic versions to identify AVM modules needing update
1. **Review**: For breaking changes, use `#web/fetch` tool to get docs from: `https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/{service}/{resource}`
1. **Review**: For breaking changes, use `#fetch` tool to get docs from: `https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/{service}/{resource}`
1. **Update**: Apply version updates and parameter changes using `#editFiles` tool
1. **Validate**: Run `bicep lint` and `bicep build` using `#runCommands` tool to ensure compliance.
1. **Output**: Summarize changes in a table format with summary of updates below.
## Tool Usage
Always use tools `#search`, `#searchResults`,`#web/fetch`, `#editFiles`, `#runCommands`, `#todos` if available. Avoid writing code to perform tasks.
Always use tools `#search`, `#searchResults`,`#fetch`, `#editFiles`, `#runCommands`, `#todos` if available. Avoid writing code to perform tasks.
## Breaking Change Policy

2
prompts/update-implementation-plan.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Update an existing implementation plan file with new or update requirements to provide new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
---
# Update Implementation Plan

2
prompts/update-llms.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Update the llms.txt file in the root folder to reflect changes in documentation or specifications following the llms.txt specification at https://llmstxt.org/'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
---
# Update LLMs.txt File

2
prompts/update-markdown-file-index.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Update a markdown file section with an index/table of files from a specified folder.'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'findTestFiles', 'githubRepo', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
---
# Update Markdown File Index

2
prompts/update-oo-component-documentation.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Update existing object-oriented component documentation following industry best practices and architectural documentation standards.'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
---
# Update Standard OO Component Documentation

2
prompts/update-specification.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: 'agent'
description: 'Update an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code.'
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
tools: ['changes', 'search/codebase', 'edit/editFiles', 'extensions', 'fetch', 'githubRepo', 'openSimpleBrowser', 'problems', 'runTasks', 'search', 'search/searchResults', 'runCommands/terminalLastCommand', 'runCommands/terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
---
# Update Specification

16
prompts/write-coding-standards-from-file.prompt.md
View File

@@ -1,7 +1,7 @@
---
agent: "agent"
description: "Write a coding standards document for a project using the coding styles from the file(s) and/or folder(s) passed as arguments in the prompt."
tools: ['createFile', 'editFiles', 'web/fetch', 'githubRepo', 'search', 'testFailure']
tools: ['createFile', 'editFiles', 'fetch', 'githubRepo', 'search', 'testFailure']
---
# Write Coding Standards From File
@@ -21,7 +21,7 @@ Parameters for the prompt have a text definition. There is one required paramete
* addToREADMEInsertions = ["atBegin", "middle", "beforeEnd", "bestFitUsingContext"];
- Default to **beforeEnd**.
* createNewFile = true;
* web/fetchStyleURL = true;
* fetchStyleURL = true;
* findInconsistencies = true;
* fixInconsistencies = true;
* newFileName = ["CONTRIBUTING.md", "STYLE.md", "CODE_OF_CONDUCT.md", "CODING_STANDARDS.md", "DEVELOPING.md", "CONTRIBUTION_GUIDE.md", "GUIDELINES.md", "PROJECT_STANDARDS.md", "BEST_PRACTICES.md", "HACKING.md"];
@@ -87,10 +87,10 @@ If any of the variable names are passed to prompt as-is, or as a similar but cle
* Create a new file using the value, or one of the possible values, from `${newFileName}`.
* If true, toggle both `${outputSpecToPrompt}` and `${addToREADME}` to false.
### `${web/fetchStyleURL} == true`
### `${fetchStyleURL} == true`
* Additionally use the data web/fetched from the links nested under level three heading `### web/fetch Links` as context for creating standards, specifications, and styling data for the new file, prompt, or `README.md`.
* For each relevant item in `### web/fetch Links`, run `#web/fetch ${item}`.
* Additionally use the data fetched from the links nested under level three heading `### Fetch Links` as context for creating standards, specifications, and styling data for the new file, prompt, or `README.md`.
* For each relevant item in `### Fetch Links`, run `#fetch ${item}`.
### `${findInconsistencies} == true`
@@ -132,11 +132,11 @@ If any of the variable names are passed to prompt as-is, or as a similar but cle
* Use the custom prompt, instructions, template, or other data passed as guiding template when composing the data for coding standards.
## **if** `${web/fetchStyleURL} == true`
## **if** `${fetchStyleURL} == true`
Depending on the programming language, for each link in list below, run `#web/fetch (URL)`, if programming language is `${fileName} == [<Language> Style Guide]`.
Depending on the programming language, for each link in list below, run `#fetch (URL)`, if programming language is `${fileName} == [<Language> Style Guide]`.
### web/fetch Links
### Fetch Links
- [C Style Guide](https://users.ece.cmu.edu/~eno/coding/CCodingStandard.html)
- [C# Style Guide](https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions)