mirror of
https://github.com/github/awesome-copilot.git
synced 2026-03-25 02:25:13 +00:00
Merge branch 'staged' into overlapping-items-workflow
This commit is contained in:
@@ -29,9 +29,9 @@
|
||||
"symbol": "🧰",
|
||||
"description": "Specialized skills for GitHub Copilot"
|
||||
},
|
||||
"collections": {
|
||||
"plugins": {
|
||||
"symbol": "🎁",
|
||||
"description": "Curated collections of related content"
|
||||
"description": "Curated plugins for GitHub Copilot"
|
||||
}
|
||||
},
|
||||
"ignoreList": [
|
||||
@@ -51,7 +51,7 @@
|
||||
"contributions": [
|
||||
"agents",
|
||||
"code",
|
||||
"collections",
|
||||
"plugins",
|
||||
"doc",
|
||||
"infra",
|
||||
"instructions",
|
||||
@@ -75,7 +75,7 @@
|
||||
"profile": "https://www.buymeacoffee.com/troystaylor",
|
||||
"contributions": [
|
||||
"agents",
|
||||
"collections",
|
||||
"plugins",
|
||||
"instructions",
|
||||
"prompts"
|
||||
]
|
||||
@@ -97,7 +97,7 @@
|
||||
"profile": "https://calva.io/",
|
||||
"contributions": [
|
||||
"agents",
|
||||
"collections",
|
||||
"plugins",
|
||||
"instructions",
|
||||
"prompts"
|
||||
]
|
||||
@@ -109,7 +109,7 @@
|
||||
"profile": "https://danielscottraynsford.com/",
|
||||
"contributions": [
|
||||
"agents",
|
||||
"collections",
|
||||
"plugins",
|
||||
"instructions",
|
||||
"prompts"
|
||||
]
|
||||
@@ -403,7 +403,7 @@
|
||||
"profile": "https://www.linkedin.com/in/griffinashe/",
|
||||
"contributions": [
|
||||
"agents",
|
||||
"collections"
|
||||
"plugins"
|
||||
]
|
||||
},
|
||||
{
|
||||
@@ -576,7 +576,7 @@
|
||||
"avatar_url": "https://avatars.githubusercontent.com/u/129743?v=4",
|
||||
"profile": "http://brunoborges.io/",
|
||||
"contributions": [
|
||||
"collections",
|
||||
"plugins",
|
||||
"instructions"
|
||||
]
|
||||
},
|
||||
@@ -865,7 +865,7 @@
|
||||
"profile": "https://github.com/kewalaka",
|
||||
"contributions": [
|
||||
"agents",
|
||||
"collections",
|
||||
"plugins",
|
||||
"instructions"
|
||||
]
|
||||
},
|
||||
@@ -957,7 +957,7 @@
|
||||
"profile": "https://www.linkedin.com/in/niksac",
|
||||
"contributions": [
|
||||
"agents",
|
||||
"collections"
|
||||
"plugins"
|
||||
]
|
||||
},
|
||||
{
|
||||
@@ -1110,7 +1110,7 @@
|
||||
"avatar_url": "https://avatars.githubusercontent.com/u/10256765?v=4",
|
||||
"profile": "https://github.com/oleksiyyurchyna",
|
||||
"contributions": [
|
||||
"collections",
|
||||
"plugins",
|
||||
"prompts"
|
||||
]
|
||||
},
|
||||
@@ -1812,6 +1812,24 @@
|
||||
"contributions": [
|
||||
"code"
|
||||
]
|
||||
},
|
||||
{
|
||||
"login": "lupritz",
|
||||
"name": "lupritz",
|
||||
"avatar_url": "https://avatars.githubusercontent.com/u/145381941?v=4",
|
||||
"profile": "https://github.com/lupritz",
|
||||
"contributions": [
|
||||
"plugin"
|
||||
]
|
||||
},
|
||||
{
|
||||
"login": "bhect0",
|
||||
"name": "Héctor Benedicte",
|
||||
"avatar_url": "https://avatars.githubusercontent.com/u/96436904?v=4",
|
||||
"profile": "https://github.com/bhect0",
|
||||
"contributions": [
|
||||
"code"
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
|
||||
@@ -34,7 +34,13 @@
|
||||
|
||||
# FillIn - pdftk-server skill reference file available permission
|
||||
|
||||
ignore-words-list = numer,wit,aks,edn,ser,ois,gir,rouge,categor,aline,ative,afterall,deques,dateA,dateB,TE,FillIn,alle,vai
|
||||
# LOD - Level of Detail
|
||||
|
||||
# InOut - template property in skills/game-engine/assets/2d-platform-game.md
|
||||
|
||||
# pixelX - template variable in skill/game-engine/assets/simple-2d-engine.md
|
||||
|
||||
ignore-words-list = numer,wit,aks,edn,ser,ois,gir,rouge,categor,aline,ative,afterall,deques,dateA,dateB,TE,FillIn,alle,vai,LOD,InOut,pixelX
|
||||
|
||||
# Skip certain files and directories
|
||||
|
||||
|
||||
20
.github/aw/actions-lock.json
vendored
20
.github/aw/actions-lock.json
vendored
@@ -1,14 +1,34 @@
|
||||
{
|
||||
"entries": {
|
||||
"actions/checkout@v6.0.2": {
|
||||
"repo": "actions/checkout",
|
||||
"version": "v6.0.2",
|
||||
"sha": "de0fac2e4500dabe0009e67214ff5f5447ce83dd"
|
||||
},
|
||||
"actions/download-artifact@v6": {
|
||||
"repo": "actions/download-artifact",
|
||||
"version": "v6",
|
||||
"sha": "018cc2cf5baa6db3ef3c5f8a56943fffe632ef53"
|
||||
},
|
||||
"actions/github-script@v8": {
|
||||
"repo": "actions/github-script",
|
||||
"version": "v8",
|
||||
"sha": "ed597411d8f924073f98dfc5c65a23a2325f34cd"
|
||||
},
|
||||
"actions/upload-artifact@v6": {
|
||||
"repo": "actions/upload-artifact",
|
||||
"version": "v6",
|
||||
"sha": "b7c566a772e6b6bfb58ed0dc250532a479d7789f"
|
||||
},
|
||||
"github/gh-aw/actions/setup@v0.45.7": {
|
||||
"repo": "github/gh-aw/actions/setup",
|
||||
"version": "v0.45.7",
|
||||
"sha": "5d8900eb6f6230c9d41a3c30af320150a2361285"
|
||||
},
|
||||
"github/gh-aw/actions/setup@v0.46.1": {
|
||||
"repo": "github/gh-aw/actions/setup",
|
||||
"version": "v0.46.1",
|
||||
"sha": "874bdd8271bf8c21902b068fb1ca6a22d2dc4b7a"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
96
.github/plugin/marketplace.json
vendored
96
.github/plugin/marketplace.json
vendored
@@ -12,271 +12,277 @@
|
||||
"plugins": [
|
||||
{
|
||||
"name": "awesome-copilot",
|
||||
"source": "./plugins/awesome-copilot",
|
||||
"source": "awesome-copilot",
|
||||
"description": "Meta prompts that help you discover and generate curated GitHub Copilot agents, instructions, prompts, and skills.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "azure-cloud-development",
|
||||
"source": "./plugins/azure-cloud-development",
|
||||
"source": "azure-cloud-development",
|
||||
"description": "Comprehensive Azure cloud development tools including Infrastructure as Code, serverless functions, architecture patterns, and cost optimization for building scalable cloud applications.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "cast-imaging",
|
||||
"source": "./plugins/cast-imaging",
|
||||
"source": "cast-imaging",
|
||||
"description": "A comprehensive collection of specialized agents for software analysis, impact assessment, structural quality advisories, and architectural review using CAST Imaging.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "clojure-interactive-programming",
|
||||
"source": "./plugins/clojure-interactive-programming",
|
||||
"source": "clojure-interactive-programming",
|
||||
"description": "Tools for REPL-first Clojure workflows featuring Clojure instructions, the interactive programming chat mode and supporting guidance.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "context-engineering",
|
||||
"source": "./plugins/context-engineering",
|
||||
"source": "context-engineering",
|
||||
"description": "Tools and techniques for maximizing GitHub Copilot effectiveness through better context management. Includes guidelines for structuring code, an agent for planning multi-file changes, and prompts for context-aware development.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "copilot-sdk",
|
||||
"source": "./plugins/copilot-sdk",
|
||||
"source": "copilot-sdk",
|
||||
"description": "Build applications with the GitHub Copilot SDK across multiple programming languages. Includes comprehensive instructions for C#, Go, Node.js/TypeScript, and Python to help you create AI-powered applications.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "csharp-dotnet-development",
|
||||
"source": "./plugins/csharp-dotnet-development",
|
||||
"source": "csharp-dotnet-development",
|
||||
"description": "Essential prompts, instructions, and chat modes for C# and .NET development including testing, documentation, and best practices.",
|
||||
"version": "1.1.0"
|
||||
},
|
||||
{
|
||||
"name": "csharp-mcp-development",
|
||||
"source": "./plugins/csharp-mcp-development",
|
||||
"source": "csharp-mcp-development",
|
||||
"description": "Complete toolkit for building Model Context Protocol (MCP) servers in C# using the official SDK. Includes instructions for best practices, a prompt for generating servers, and an expert chat mode for guidance.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "database-data-management",
|
||||
"source": "./plugins/database-data-management",
|
||||
"source": "database-data-management",
|
||||
"description": "Database administration, SQL optimization, and data management tools for PostgreSQL, SQL Server, and general database development best practices.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "dataverse",
|
||||
"source": "dataverse",
|
||||
"description": "Comprehensive collection for Microsoft Dataverse integrations. Includes MCP setup commands.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "dataverse-sdk-for-python",
|
||||
"source": "./plugins/dataverse-sdk-for-python",
|
||||
"source": "dataverse-sdk-for-python",
|
||||
"description": "Comprehensive collection for building production-ready Python integrations with Microsoft Dataverse. Includes official documentation, best practices, advanced features, file operations, and code generation prompts.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "devops-oncall",
|
||||
"source": "./plugins/devops-oncall",
|
||||
"source": "devops-oncall",
|
||||
"description": "A focused set of prompts, instructions, and a chat mode to help triage incidents and respond quickly with DevOps tools and Azure resources.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "edge-ai-tasks",
|
||||
"source": "./plugins/edge-ai-tasks",
|
||||
"source": "edge-ai-tasks",
|
||||
"description": "Task Researcher and Task Planner for intermediate to expert users and large codebases - Brought to you by microsoft/edge-ai",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "frontend-web-dev",
|
||||
"source": "./plugins/frontend-web-dev",
|
||||
"source": "frontend-web-dev",
|
||||
"description": "Essential prompts, instructions, and chat modes for modern frontend web development including React, Angular, Vue, TypeScript, and CSS frameworks.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "gem-team",
|
||||
"source": "./plugins/gem-team",
|
||||
"source": "gem-team",
|
||||
"description": "A modular multi-agent team for complex project execution with DAG-based planning, parallel execution, TDD verification, and automated testing.",
|
||||
"version": "1.1.0"
|
||||
},
|
||||
{
|
||||
"name": "go-mcp-development",
|
||||
"source": "./plugins/go-mcp-development",
|
||||
"source": "go-mcp-development",
|
||||
"description": "Complete toolkit for building Model Context Protocol (MCP) servers in Go using the official github.com/modelcontextprotocol/go-sdk. Includes instructions for best practices, a prompt for generating servers, and an expert chat mode for guidance.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "java-development",
|
||||
"source": "./plugins/java-development",
|
||||
"source": "java-development",
|
||||
"description": "Comprehensive collection of prompts and instructions for Java development including Spring Boot, Quarkus, testing, documentation, and best practices.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "java-mcp-development",
|
||||
"source": "./plugins/java-mcp-development",
|
||||
"source": "java-mcp-development",
|
||||
"description": "Complete toolkit for building Model Context Protocol servers in Java using the official MCP Java SDK with reactive streams and Spring Boot integration.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "kotlin-mcp-development",
|
||||
"source": "./plugins/kotlin-mcp-development",
|
||||
"source": "kotlin-mcp-development",
|
||||
"description": "Complete toolkit for building Model Context Protocol (MCP) servers in Kotlin using the official io.modelcontextprotocol:kotlin-sdk library. Includes instructions for best practices, a prompt for generating servers, and an expert chat mode for guidance.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "mcp-m365-copilot",
|
||||
"source": "./plugins/mcp-m365-copilot",
|
||||
"source": "mcp-m365-copilot",
|
||||
"description": "Comprehensive collection for building declarative agents with Model Context Protocol integration for Microsoft 365 Copilot",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "openapi-to-application-csharp-dotnet",
|
||||
"source": "./plugins/openapi-to-application-csharp-dotnet",
|
||||
"source": "openapi-to-application-csharp-dotnet",
|
||||
"description": "Generate production-ready .NET applications from OpenAPI specifications. Includes ASP.NET Core project scaffolding, controller generation, entity framework integration, and C# best practices.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "openapi-to-application-go",
|
||||
"source": "./plugins/openapi-to-application-go",
|
||||
"source": "openapi-to-application-go",
|
||||
"description": "Generate production-ready Go applications from OpenAPI specifications. Includes project scaffolding, handler generation, middleware setup, and Go best practices for REST APIs.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "openapi-to-application-java-spring-boot",
|
||||
"source": "./plugins/openapi-to-application-java-spring-boot",
|
||||
"source": "openapi-to-application-java-spring-boot",
|
||||
"description": "Generate production-ready Spring Boot applications from OpenAPI specifications. Includes project scaffolding, REST controller generation, service layer organization, and Spring Boot best practices.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "openapi-to-application-nodejs-nestjs",
|
||||
"source": "./plugins/openapi-to-application-nodejs-nestjs",
|
||||
"source": "openapi-to-application-nodejs-nestjs",
|
||||
"description": "Generate production-ready NestJS applications from OpenAPI specifications. Includes project scaffolding, controller and service generation, TypeScript best practices, and enterprise patterns.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "openapi-to-application-python-fastapi",
|
||||
"source": "./plugins/openapi-to-application-python-fastapi",
|
||||
"source": "openapi-to-application-python-fastapi",
|
||||
"description": "Generate production-ready FastAPI applications from OpenAPI specifications. Includes project scaffolding, route generation, dependency injection, and Python best practices for async APIs.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "ospo-sponsorship",
|
||||
"source": "./plugins/ospo-sponsorship",
|
||||
"source": "ospo-sponsorship",
|
||||
"description": "Tools and resources for Open Source Program Offices (OSPOs) to identify, evaluate, and manage sponsorship of open source dependencies through GitHub Sponsors, Open Collective, and other funding platforms.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "partners",
|
||||
"source": "./plugins/partners",
|
||||
"source": "partners",
|
||||
"description": "Custom agents that have been created by GitHub partners",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "pcf-development",
|
||||
"source": "./plugins/pcf-development",
|
||||
"source": "pcf-development",
|
||||
"description": "Complete toolkit for developing custom code components using Power Apps Component Framework for model-driven and canvas apps",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "php-mcp-development",
|
||||
"source": "./plugins/php-mcp-development",
|
||||
"source": "php-mcp-development",
|
||||
"description": "Comprehensive resources for building Model Context Protocol servers using the official PHP SDK with attribute-based discovery, including best practices, project generation, and expert assistance",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "polyglot-test-agent",
|
||||
"source": "./plugins/polyglot-test-agent",
|
||||
"source": "polyglot-test-agent",
|
||||
"description": "Multi-agent pipeline for generating comprehensive unit tests across any programming language. Orchestrates research, planning, and implementation phases using specialized agents to produce tests that compile, pass, and follow project conventions.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "power-apps-code-apps",
|
||||
"source": "./plugins/power-apps-code-apps",
|
||||
"source": "power-apps-code-apps",
|
||||
"description": "Complete toolkit for Power Apps Code Apps development including project scaffolding, development standards, and expert guidance for building code-first applications with Power Platform integration.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "power-bi-development",
|
||||
"source": "./plugins/power-bi-development",
|
||||
"source": "power-bi-development",
|
||||
"description": "Comprehensive Power BI development resources including data modeling, DAX optimization, performance tuning, visualization design, security best practices, and DevOps/ALM guidance for building enterprise-grade Power BI solutions.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "power-platform-mcp-connector-development",
|
||||
"source": "./plugins/power-platform-mcp-connector-development",
|
||||
"source": "power-platform-mcp-connector-development",
|
||||
"description": "Complete toolkit for developing Power Platform custom connectors with Model Context Protocol integration for Microsoft Copilot Studio",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "project-planning",
|
||||
"source": "./plugins/project-planning",
|
||||
"source": "project-planning",
|
||||
"description": "Tools and guidance for software project planning, feature breakdown, epic management, implementation planning, and task organization for development teams.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "python-mcp-development",
|
||||
"source": "./plugins/python-mcp-development",
|
||||
"source": "python-mcp-development",
|
||||
"description": "Complete toolkit for building Model Context Protocol (MCP) servers in Python using the official SDK with FastMCP. Includes instructions for best practices, a prompt for generating servers, and an expert chat mode for guidance.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "ruby-mcp-development",
|
||||
"source": "./plugins/ruby-mcp-development",
|
||||
"source": "ruby-mcp-development",
|
||||
"description": "Complete toolkit for building Model Context Protocol servers in Ruby using the official MCP Ruby SDK gem with Rails integration support.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "rug-agentic-workflow",
|
||||
"source": "./plugins/rug-agentic-workflow",
|
||||
"source": "rug-agentic-workflow",
|
||||
"description": "Three-agent workflow for orchestrated software delivery with an orchestrator plus implementation and QA subagents.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "rust-mcp-development",
|
||||
"source": "./plugins/rust-mcp-development",
|
||||
"source": "rust-mcp-development",
|
||||
"description": "Build high-performance Model Context Protocol servers in Rust using the official rmcp SDK with async/await, procedural macros, and type-safe implementations.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "security-best-practices",
|
||||
"source": "./plugins/security-best-practices",
|
||||
"source": "security-best-practices",
|
||||
"description": "Security frameworks, accessibility guidelines, performance optimization, and code quality best practices for building secure, maintainable, and high-performance applications.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "software-engineering-team",
|
||||
"source": "./plugins/software-engineering-team",
|
||||
"source": "software-engineering-team",
|
||||
"description": "7 specialized agents covering the full software development lifecycle from UX design and architecture to security and DevOps.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "structured-autonomy",
|
||||
"source": "./plugins/structured-autonomy",
|
||||
"source": "structured-autonomy",
|
||||
"description": "Premium planning, thrifty implementation",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "swift-mcp-development",
|
||||
"source": "./plugins/swift-mcp-development",
|
||||
"source": "swift-mcp-development",
|
||||
"description": "Comprehensive collection for building Model Context Protocol servers in Swift using the official MCP Swift SDK with modern concurrency features.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "technical-spike",
|
||||
"source": "./plugins/technical-spike",
|
||||
"source": "technical-spike",
|
||||
"description": "Tools for creation, management and research of technical spikes to reduce unknowns and assumptions before proceeding to specification and implementation of solutions.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "testing-automation",
|
||||
"source": "./plugins/testing-automation",
|
||||
"source": "testing-automation",
|
||||
"description": "Comprehensive collection for writing tests, test automation, and test-driven development including unit tests, integration tests, and end-to-end testing strategies.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "typescript-mcp-development",
|
||||
"source": "./plugins/typescript-mcp-development",
|
||||
"source": "typescript-mcp-development",
|
||||
"description": "Complete toolkit for building Model Context Protocol (MCP) servers in TypeScript/Node.js using the official SDK. Includes instructions for best practices, a prompt for generating servers, and an expert chat mode for guidance.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "typespec-m365-copilot",
|
||||
"source": "./plugins/typespec-m365-copilot",
|
||||
"source": "typespec-m365-copilot",
|
||||
"description": "Comprehensive collection of prompts, instructions, and resources for building declarative agents and API plugins using TypeSpec for Microsoft 365 Copilot extensibility.",
|
||||
"version": "1.0.0"
|
||||
}
|
||||
|
||||
7
.github/pull_request_template.md
vendored
7
.github/pull_request_template.md
vendored
@@ -1,10 +1,10 @@
|
||||
## Pull Request Checklist
|
||||
|
||||
- [ ] I have read and followed the [CONTRIBUTING.md](https://github.com/github/awesome-copilot/blob/main/CONTRIBUTING.md) guidelines.
|
||||
- [ ] My contribution adds a new instruction, prompt, agent, or skill file in the correct directory.
|
||||
- [ ] My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
|
||||
- [ ] The file follows the required naming convention.
|
||||
- [ ] The content is clearly structured and follows the example format.
|
||||
- [ ] I have tested my instructions, prompt, agent, or skill with GitHub Copilot.
|
||||
- [ ] I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
|
||||
- [ ] I have run `npm start` and verified that `README.md` is up to date.
|
||||
|
||||
---
|
||||
@@ -22,7 +22,8 @@
|
||||
- [ ] New agent file.
|
||||
- [ ] New plugin.
|
||||
- [ ] New skill file.
|
||||
- [ ] Update to existing instruction, prompt, agent, plugin, or skill.
|
||||
- [ ] New agentic workflow.
|
||||
- [ ] Update to existing instruction, prompt, agent, plugin, skill, or workflow.
|
||||
- [ ] Other (please specify):
|
||||
|
||||
---
|
||||
|
||||
3
.github/workflows/publish.yml
vendored
3
.github/workflows/publish.yml
vendored
@@ -49,5 +49,6 @@ jobs:
|
||||
git config user.name "github-actions[bot]"
|
||||
git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
|
||||
git add -A
|
||||
git commit -m "chore: publish from staged [skip ci]" --allow-empty
|
||||
git add -f plugins/*/agents/ plugins/*/skills/
|
||||
git commit -m "chore: publish from staged" --allow-empty
|
||||
git push origin HEAD:main --force
|
||||
|
||||
129
.github/workflows/validate-agentic-workflows-pr.yml
vendored
Normal file
129
.github/workflows/validate-agentic-workflows-pr.yml
vendored
Normal file
@@ -0,0 +1,129 @@
|
||||
name: Validate Agentic Workflow Contributions
|
||||
|
||||
on:
|
||||
pull_request:
|
||||
branches: [staged]
|
||||
types: [opened, synchronize, reopened]
|
||||
paths:
|
||||
- "workflows/**"
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
pull-requests: write
|
||||
|
||||
jobs:
|
||||
check-forbidden-files:
|
||||
name: Block forbidden files
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Checkout code
|
||||
uses: actions/checkout@v4
|
||||
with:
|
||||
fetch-depth: 0
|
||||
|
||||
- name: Check for forbidden files
|
||||
id: check
|
||||
run: |
|
||||
# Check for YAML/lock files in workflows/ and any .github/ modifications
|
||||
# Allow .github/aw/actions-lock.json which is needed for workflow compilation
|
||||
forbidden=$(git diff --name-only --diff-filter=ACM origin/${{ github.base_ref }}...HEAD -- \
|
||||
'workflows/**/*.yml' \
|
||||
'workflows/**/*.yaml' \
|
||||
'workflows/**/*.lock.yml' \
|
||||
'.github/*' \
|
||||
'.github/**' \
|
||||
| grep -v '^\.github/aw/actions-lock\.json$' \
|
||||
| grep -v '^\.github/workflows/validate-agentic-workflows-pr\.yml$' \
|
||||
|| true)
|
||||
|
||||
if [ -n "$forbidden" ]; then
|
||||
echo "❌ Forbidden files detected:"
|
||||
echo "$forbidden"
|
||||
echo "files<<EOF" >> "$GITHUB_OUTPUT"
|
||||
echo "$forbidden" >> "$GITHUB_OUTPUT"
|
||||
echo "EOF" >> "$GITHUB_OUTPUT"
|
||||
exit 1
|
||||
else
|
||||
echo "✅ No forbidden files found"
|
||||
fi
|
||||
|
||||
- name: Comment on PR
|
||||
if: failure()
|
||||
uses: marocchino/sticky-pull-request-comment@v2
|
||||
with:
|
||||
header: workflow-forbidden-files
|
||||
message: |
|
||||
## 🚫 Forbidden files in `workflows/`
|
||||
|
||||
Only `.md` markdown files are accepted in the `workflows/` directory. The following are **not allowed**:
|
||||
- Compiled workflow files (`.yml`, `.yaml`, `.lock.yml`) — could contain untrusted Actions code
|
||||
- `.github/` modifications — workflow contributions must not modify repository configuration
|
||||
|
||||
**Files that must be removed:**
|
||||
```
|
||||
${{ steps.check.outputs.files }}
|
||||
```
|
||||
|
||||
Contributors provide the workflow **source** (`.md`) only. Compilation happens downstream via `gh aw compile`.
|
||||
|
||||
Please remove these files and push again.
|
||||
|
||||
compile-workflows:
|
||||
name: Compile and validate
|
||||
needs: check-forbidden-files
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Checkout code
|
||||
uses: actions/checkout@v4
|
||||
|
||||
- name: Install gh-aw CLI
|
||||
uses: github/gh-aw/actions/setup-cli@main
|
||||
|
||||
- name: Compile workflow files
|
||||
id: compile
|
||||
run: |
|
||||
exit_code=0
|
||||
found=0
|
||||
|
||||
# Find all .md files directly in workflows/
|
||||
for workflow_file in workflows/*.md; do
|
||||
[ -f "$workflow_file" ] || continue
|
||||
|
||||
found=$((found + 1))
|
||||
echo "::group::Compiling $workflow_file"
|
||||
if gh aw compile --validate "$workflow_file"; then
|
||||
echo "✅ $workflow_file compiled successfully"
|
||||
else
|
||||
echo "❌ $workflow_file failed to compile"
|
||||
exit_code=1
|
||||
fi
|
||||
echo "::endgroup::"
|
||||
done
|
||||
|
||||
if [ "$found" -eq 0 ]; then
|
||||
echo "No workflow .md files found to validate."
|
||||
else
|
||||
echo "Validated $found workflow file(s)."
|
||||
fi
|
||||
|
||||
echo "status=$( [ $exit_code -eq 0 ] && echo success || echo failure )" >> "$GITHUB_OUTPUT"
|
||||
exit $exit_code
|
||||
|
||||
- name: Comment on PR if compilation failed
|
||||
if: failure()
|
||||
uses: marocchino/sticky-pull-request-comment@v2
|
||||
with:
|
||||
header: workflow-validation
|
||||
message: |
|
||||
## ❌ Agentic Workflow compilation failed
|
||||
|
||||
One or more workflow files in `workflows/` failed to compile with `gh aw compile --validate`.
|
||||
|
||||
Please fix the errors and push again. You can test locally with:
|
||||
|
||||
```bash
|
||||
gh extension install github/gh-aw
|
||||
gh aw compile --validate <your-workflow-file>.md
|
||||
```
|
||||
|
||||
See the [Agentic Workflows documentation](https://github.github.com/gh-aw) for help.
|
||||
1
.github/workflows/validate-readme.yml
vendored
1
.github/workflows/validate-readme.yml
vendored
@@ -9,6 +9,7 @@ on:
|
||||
- "prompts/**"
|
||||
- "agents/**"
|
||||
- "plugins/**"
|
||||
- "workflows/**"
|
||||
- "*.js"
|
||||
- "README.md"
|
||||
- "docs/**"
|
||||
|
||||
5
.gitignore
vendored
5
.gitignore
vendored
@@ -10,6 +10,11 @@ reports/
|
||||
# Generated files
|
||||
/llms.txt
|
||||
|
||||
# Materialized plugin files (generated by CI via eng/materialize-plugins.mjs)
|
||||
plugins/*/agents/
|
||||
plugins/*/commands/
|
||||
plugins/*/skills/
|
||||
|
||||
# Website build artifacts
|
||||
website/dist/
|
||||
website/.astro/
|
||||
|
||||
59
AGENTS.md
59
AGENTS.md
@@ -2,13 +2,13 @@
|
||||
|
||||
## Project Overview
|
||||
|
||||
The Awesome GitHub Copilot repository is a community-driven collection of custom agents, prompts, and instructions designed to enhance GitHub Copilot experiences across various domains, languages, and use cases. The project includes:
|
||||
The Awesome GitHub Copilot repository is a community-driven collection of custom agents and instructions designed to enhance GitHub Copilot experiences across various domains, languages, and use cases. The project includes:
|
||||
|
||||
- **Agents** - Specialized GitHub Copilot agents that integrate with MCP servers
|
||||
- **Prompts** - Task-specific prompts for code generation and problem-solving
|
||||
- **Instructions** - Coding standards and best practices applied to specific file patterns
|
||||
- **Skills** - Self-contained folders with instructions and bundled resources for specialized tasks
|
||||
- **Hooks** - Automated workflows triggered by specific events during development
|
||||
- **Workflows** - [Agentic Workflows](https://github.github.com/gh-aw) for AI-powered repository automation in GitHub Actions
|
||||
- **Plugins** - Installable packages that group related agents, commands, and skills around specific themes
|
||||
|
||||
## Repository Structure
|
||||
@@ -16,10 +16,10 @@ The Awesome GitHub Copilot repository is a community-driven collection of custom
|
||||
```
|
||||
.
|
||||
├── agents/ # Custom GitHub Copilot agent definitions (.agent.md files)
|
||||
├── prompts/ # Task-specific prompts (.prompt.md files)
|
||||
├── instructions/ # Coding standards and guidelines (.instructions.md files)
|
||||
├── skills/ # Agent Skills folders (each with SKILL.md and optional bundled assets)
|
||||
├── hooks/ # Automated workflow hooks (folders with README.md + hooks.json)
|
||||
├── workflows/ # Agentic Workflows (.md files for GitHub Actions automation)
|
||||
├── plugins/ # Installable plugin packages (folders with plugin.json)
|
||||
├── docs/ # Documentation for different resource types
|
||||
├── eng/ # Build and automation scripts
|
||||
@@ -53,9 +53,9 @@ npm run skill:create -- --name <skill-name>
|
||||
|
||||
## Development Workflow
|
||||
|
||||
### Working with Agents, Prompts, Instructions, Skills, and Hooks
|
||||
### Working with Agents, Instructions, Skills, and Hooks
|
||||
|
||||
All agent files (`*.agent.md`), prompt files (`*.prompt.md`), and instruction files (`*.instructions.md`) must include proper markdown front matter. Agent Skills are folders containing a `SKILL.md` file with frontmatter and optional bundled assets. Hooks are folders containing a `README.md` with frontmatter and a `hooks.json` configuration file:
|
||||
All agent files (`*.agent.md`) and instruction files (`*.instructions.md`) must include proper markdown front matter. Agent Skills are folders containing a `SKILL.md` file with frontmatter and optional bundled assets. Hooks are folders containing a `README.md` with frontmatter and a `hooks.json` configuration file:
|
||||
|
||||
#### Agent Files (*.agent.md)
|
||||
- Must have `description` field (wrapped in single quotes)
|
||||
@@ -63,13 +63,6 @@ All agent files (`*.agent.md`), prompt files (`*.prompt.md`), and instruction fi
|
||||
- Recommended to include `tools` field
|
||||
- Strongly recommended to specify `model` field
|
||||
|
||||
#### Prompt Files (*.prompt.md)
|
||||
- Must have `agent` field (value should be `'agent'` wrapped in single quotes)
|
||||
- Must have `description` field (wrapped in single quotes, not empty)
|
||||
- File names should be lower case with words separated by hyphens
|
||||
- Recommended to specify `tools` if applicable
|
||||
- Strongly recommended to specify `model` field
|
||||
|
||||
#### Instruction Files (*.instructions.md)
|
||||
- Must have `description` field (wrapped in single quotes, not empty)
|
||||
- Must have `applyTo` field specifying file patterns (e.g., `'**.js, **.ts'`)
|
||||
@@ -96,6 +89,15 @@ All agent files (`*.agent.md`), prompt files (`*.prompt.md`), and instruction fi
|
||||
- Follow the [GitHub Copilot hooks specification](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/use-hooks)
|
||||
- Optionally includes `tags` field for categorization
|
||||
|
||||
#### Workflow Files (workflows/*.md)
|
||||
- Each workflow is a standalone `.md` file in the `workflows/` directory
|
||||
- Must have `name` field (human-readable name)
|
||||
- Must have `description` field (wrapped in single quotes, not empty)
|
||||
- Contains agentic workflow frontmatter (`on`, `permissions`, `safe-outputs`) and natural language instructions
|
||||
- File names should be lower case with words separated by hyphens
|
||||
- Only `.md` files are accepted — `.yml`, `.yaml`, and `.lock.yml` files are blocked by CI
|
||||
- Follow the [GitHub Agentic Workflows specification](https://github.github.com/gh-aw/reference/workflow-structure/)
|
||||
|
||||
#### Plugin Folders (plugins/*)
|
||||
- Each plugin is a folder containing a `.github/plugin/plugin.json` file with metadata
|
||||
- plugin.json must have `name` field (matching the folder name)
|
||||
@@ -107,9 +109,9 @@ All agent files (`*.agent.md`), prompt files (`*.prompt.md`), and instruction fi
|
||||
|
||||
### Adding New Resources
|
||||
|
||||
When adding a new agent, prompt, instruction, skill, hook, or plugin:
|
||||
When adding a new agent, instruction, skill, hook, workflow, or plugin:
|
||||
|
||||
**For Agents, Prompts, and Instructions:**
|
||||
**For Agents and Instructions:**
|
||||
1. Create the file with proper front matter
|
||||
2. Add the file to the appropriate directory
|
||||
3. Update the README.md by running: `npm run build`
|
||||
@@ -125,6 +127,14 @@ When adding a new agent, prompt, instruction, skill, hook, or plugin:
|
||||
7. Verify the hook appears in the generated README
|
||||
|
||||
|
||||
**For Workflows:**
|
||||
1. Create a new `.md` file in `workflows/` with a descriptive name (e.g., `daily-issues-report.md`)
|
||||
2. Include frontmatter with `name` and `description`, plus agentic workflow fields (`on`, `permissions`, `safe-outputs`)
|
||||
3. Compile with `gh aw compile --validate` to verify it's valid
|
||||
4. Update the README.md by running: `npm run build`
|
||||
5. Verify the workflow appears in the generated README
|
||||
|
||||
|
||||
**For Skills:**
|
||||
1. Run `npm run skill:create` to scaffold a new skill folder
|
||||
2. Edit the generated SKILL.md file with your instructions
|
||||
@@ -186,7 +196,7 @@ When creating a pull request:
|
||||
3. **File naming**: Verify all new files follow the lower-case-with-hyphens naming convention
|
||||
4. **Build check**: Run `npm run build` before committing to verify README generation
|
||||
5. **Line endings**: **Always run `bash scripts/fix-line-endings.sh`** to normalize line endings to LF (Unix-style)
|
||||
6. **Description**: Provide a clear description of what your agent/prompt/instruction does
|
||||
6. **Description**: Provide a clear description of what your agent/instruction does
|
||||
7. **Testing**: If adding a plugin, run `npm run plugin:validate` to ensure validity
|
||||
|
||||
### Pre-commit Checklist
|
||||
@@ -201,13 +211,6 @@ Before submitting your PR, ensure you have:
|
||||
|
||||
### Code Review Checklist
|
||||
|
||||
For prompt files (*.prompt.md):
|
||||
- [ ] Has markdown front matter
|
||||
- [ ] Has `agent` field (value should be `'agent'` wrapped in single quotes)
|
||||
- [ ] Has non-empty `description` field wrapped in single quotes
|
||||
- [ ] File name is lower case with hyphens
|
||||
- [ ] Includes `model` field (strongly recommended)
|
||||
|
||||
For instruction files (*.instructions.md):
|
||||
- [ ] Has markdown front matter
|
||||
- [ ] Has non-empty `description` field wrapped in single quotes
|
||||
@@ -241,6 +244,16 @@ For hook folders (hooks/*/):
|
||||
- [ ] Follows [GitHub Copilot hooks specification](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/use-hooks)
|
||||
- [ ] Optionally includes `tags` array field for categorization
|
||||
|
||||
For workflow files (workflows/*.md):
|
||||
- [ ] File has markdown front matter
|
||||
- [ ] Has `name` field with human-readable name
|
||||
- [ ] Has non-empty `description` field wrapped in single quotes
|
||||
- [ ] File name is lower case with hyphens
|
||||
- [ ] Contains `on` and `permissions` in frontmatter
|
||||
- [ ] Workflow uses least-privilege permissions and safe outputs
|
||||
- [ ] No `.yml`, `.yaml`, or `.lock.yml` files included
|
||||
- [ ] Follows [GitHub Agentic Workflows specification](https://github.github.com/gh-aw/reference/workflow-structure/)
|
||||
|
||||
For plugins (plugins/*/):
|
||||
- [ ] Directory contains a `.github/plugin/plugin.json` file
|
||||
- [ ] Directory contains a `README.md` file
|
||||
@@ -262,7 +275,7 @@ This is a community-driven project. Contributions are welcome! Please see:
|
||||
|
||||
## MCP Server
|
||||
|
||||
The repository includes an MCP (Model Context Protocol) Server that provides prompts for searching and installing resources directly from this repository. Docker is required to run the server.
|
||||
The repository includes an MCP (Model Context Protocol) Server for searching and installing resources directly from this repository. Docker is required to run the server.
|
||||
|
||||
## License
|
||||
|
||||
|
||||
150
CONTRIBUTING.md
150
CONTRIBUTING.md
@@ -1,6 +1,25 @@
|
||||
# Contributing to Awesome GitHub Copilot
|
||||
|
||||
Thank you for your interest in contributing to the Awesome GitHub Copilot repository! We welcome contributions from the community to help expand our collection of custom instructions and prompts.
|
||||
Thank you for your interest in contributing to the Awesome GitHub Copilot repository! We welcome contributions from the community to help expand our collection of custom instructions and skills.
|
||||
|
||||
## Table of Contents
|
||||
|
||||
- [How to Contribute](#how-to-contribute)
|
||||
- [Adding Instructions](#adding-instructions)
|
||||
- [Adding Prompts](#adding-prompts)
|
||||
- [Adding Agents](#adding-agents)
|
||||
- [Adding Skills](#adding-skills)
|
||||
- [Adding Plugins](#adding-plugins)
|
||||
- [Adding Hooks](#adding-hooks)
|
||||
- [Adding Agentic Workflows](#adding-agentic-workflows)
|
||||
- [Submitting Your Contribution](#submitting-your-contribution)
|
||||
- [What We Accept](#what-we-accept)
|
||||
- [What We Don't Accept](#what-we-dont-accept)
|
||||
- [Quality Guidelines](#quality-guidelines)
|
||||
- [Contributor Recognition](#contributor-recognition)
|
||||
- [Contribution Types](#contribution-types)
|
||||
- [Code of Conduct](#code-of-conduct)
|
||||
- [License](#license)
|
||||
|
||||
## How to Contribute
|
||||
|
||||
@@ -33,34 +52,6 @@ description: 'Instructions for customizing GitHub Copilot behavior for specific
|
||||
- Any additional context or examples
|
||||
```
|
||||
|
||||
### Adding Prompts
|
||||
|
||||
Prompts are ready-to-use templates for specific development scenarios and tasks.
|
||||
|
||||
1. **Create your prompt file**: Add a new `.prompt.md` file in the `prompts/` directory
|
||||
2. **Follow the naming convention**: Use descriptive, lowercase filenames with hyphens and the `.prompt.md` extension (e.g., `react-component-generator.prompt.md`)
|
||||
3. **Include frontmatter**: Add metadata at the top of your file (optional but recommended)
|
||||
4. **Structure your prompt**: Provide clear context and specific instructions
|
||||
|
||||
#### Example prompt format
|
||||
|
||||
```markdown
|
||||
---
|
||||
agent: 'agent'
|
||||
tools: ['codebase', 'terminalCommand']
|
||||
description: 'Brief description of what this prompt does'
|
||||
---
|
||||
|
||||
# Prompt Title
|
||||
|
||||
Your goal is to...
|
||||
|
||||
## Specific Instructions
|
||||
|
||||
- Clear, actionable instructions
|
||||
- Include examples where helpful
|
||||
```
|
||||
|
||||
### Adding an Agent
|
||||
|
||||
Agents are specialized configurations that transform GitHub Copilot Chat into domain-specific assistants or personas for particular development scenarios.
|
||||
@@ -113,7 +104,7 @@ Skills are self-contained folders in the `skills/` directory that include a `SKI
|
||||
|
||||
### Adding Plugins
|
||||
|
||||
Plugins group related agents, commands (prompts), and skills around specific themes or workflows, making it easy for users to install comprehensive toolkits via GitHub Copilot CLI.
|
||||
Plugins group related agents, commands, and skills around specific themes or workflows, making it easy for users to install comprehensive toolkits via GitHub Copilot CLI.
|
||||
|
||||
1. **Create your plugin**: Run `npm run plugin:create` to scaffold a new plugin
|
||||
2. **Follow the naming convention**: Use descriptive, lowercase folder names with hyphens (e.g., `python-web-development`)
|
||||
@@ -161,17 +152,106 @@ plugins/my-plugin-id/
|
||||
- **Clear purpose**: The plugin should solve a specific problem or workflow
|
||||
- **Validate before submitting**: Run `npm run plugin:validate` to ensure your plugin is valid
|
||||
|
||||
### Adding Hooks
|
||||
|
||||
Hooks enable automated workflows triggered by specific events during GitHub Copilot coding agent sessions, such as session start, session end, user prompts, and tool usage.
|
||||
|
||||
1. **Create a new hook folder**: Add a new folder in the `hooks/` directory with a descriptive, lowercase name using hyphens (e.g., `session-logger`)
|
||||
2. **Create `README.md`**: Add a `README.md` file with frontmatter including `name`, `description`, and optionally `tags`
|
||||
3. **Create `hooks.json`**: Add a `hooks.json` file with hook configuration following the [GitHub Copilot hooks specification](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/use-hooks)
|
||||
4. **Add bundled scripts**: Include any scripts or assets the hook needs, and make them executable (`chmod +x script.sh`)
|
||||
5. **Update the README**: Run `npm run build` to update the generated README tables
|
||||
|
||||
#### Example hook structure
|
||||
|
||||
```
|
||||
hooks/my-hook/
|
||||
├── README.md # Hook documentation with frontmatter
|
||||
├── hooks.json # Hook event configuration
|
||||
└── my-script.sh # Bundled script(s)
|
||||
```
|
||||
|
||||
#### Example README.md frontmatter
|
||||
|
||||
```markdown
|
||||
---
|
||||
name: 'My Hook Name'
|
||||
description: 'Brief description of what this hook does'
|
||||
tags: ['logging', 'automation']
|
||||
---
|
||||
|
||||
# My Hook Name
|
||||
|
||||
Detailed documentation about the hook...
|
||||
```
|
||||
|
||||
#### Hook Guidelines
|
||||
|
||||
- **Event configuration**: Define hook events in `hooks.json` — supported events include session start, session end, user prompts, and tool usage
|
||||
- **Executable scripts**: Ensure all bundled scripts are executable and referenced in both `README.md` and `hooks.json`
|
||||
- **Privacy aware**: Be mindful of what data your hook collects or logs
|
||||
- **Clear documentation**: Explain installation steps, configuration options, and what the hook does
|
||||
- Follow the [GitHub Copilot hooks specification](https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/use-hooks)
|
||||
|
||||
### Adding Agentic Workflows
|
||||
|
||||
[Agentic Workflows](https://github.github.com/gh-aw) are AI-powered repository automations that run coding agents in GitHub Actions. Defined in markdown with natural language instructions, they enable scheduled and event-triggered automation with built-in guardrails.
|
||||
|
||||
1. **Create your workflow file** with a new `.md` file in the `workflows/` directory (e.g., [`daily-issues-report.md`](./workflows/daily-issues-report.md))
|
||||
2. **Include frontmatter** with `name` and `description`, followed by agentic workflow frontmatter (`on`, `permissions`, `safe-outputs`) and natural language instructions
|
||||
3. **Test locally** with `gh aw compile --validate --no-emit daily-issues-report.md` to verify it's valid
|
||||
4. **Update the README** with `npm run build` to update the generated README tables
|
||||
|
||||
> **Note:** Only `.md` files are accepted — do not include compiled `.lock.yml` or `.yml` files. CI will block them.
|
||||
|
||||
#### Workflow file example
|
||||
|
||||
```markdown
|
||||
---
|
||||
name: "Daily Issues Report"
|
||||
description: "Generates a daily summary of open issues and recent activity as a GitHub issue"
|
||||
on:
|
||||
schedule: daily on weekdays
|
||||
permissions:
|
||||
contents: read
|
||||
issues: read
|
||||
safe-outputs:
|
||||
create-issue:
|
||||
title-prefix: "[daily-report] "
|
||||
labels: [report]
|
||||
---
|
||||
|
||||
## Daily Issues Report
|
||||
|
||||
Create a daily summary of open issues for the team.
|
||||
|
||||
## What to Include
|
||||
|
||||
- New issues opened in the last 24 hours
|
||||
- Issues closed or resolved
|
||||
- Stale issues that need attention
|
||||
```
|
||||
|
||||
#### Workflow Guidelines
|
||||
|
||||
- **Security first**: Use least-privilege permissions and safe outputs instead of direct write access
|
||||
- **Clear instructions**: Write clear natural language instructions in the workflow body
|
||||
- **Descriptive names**: Use lowercase filenames with hyphens (e.g., `daily-issues-report.md`)
|
||||
- **Test locally**: Use `gh aw compile --validate` to verify your workflow compiles
|
||||
- **No compiled files**: Only submit the `.md` source — `.lock.yml` and `.yml` files are not accepted
|
||||
- Learn more at the [Agentic Workflows documentation](https://github.github.com/gh-aw)
|
||||
|
||||
## Submitting Your Contribution
|
||||
|
||||
1. **Fork this repository**
|
||||
2. **Create a new branch** for your contribution
|
||||
3. **Add your instruction, prompt file, chatmode, or plugin** following the guidelines above
|
||||
3. **Add your instruction, skills, agents, workflow, or plugin** following the guidelines above
|
||||
4. **Run the update script**: `npm start` to update the README with your new file (make sure you run `npm install` first if you haven't already)
|
||||
- A GitHub Actions workflow will verify that this step was performed correctly
|
||||
- If the README.md would be modified by running the script, the PR check will fail with a comment showing the required changes
|
||||
5. **Submit a pull request** targeting the `staged` branch with:
|
||||
- A clear title describing your contribution
|
||||
- A brief description of what your instruction/prompt does
|
||||
- A brief description of what your instruction/skill/agent does
|
||||
- Any relevant context or usage notes
|
||||
|
||||
> [!IMPORTANT]
|
||||
@@ -206,7 +286,7 @@ To maintain a safe, responsible, and constructive community, we will **not accep
|
||||
## Quality Guidelines
|
||||
|
||||
- **Be specific**: Generic instructions are less helpful than specific, actionable guidance
|
||||
- **Test your content**: Ensure your instructions or prompts work well with GitHub Copilot
|
||||
- **Test your content**: Ensure your instructions or skills work well with GitHub Copilot
|
||||
- **Follow conventions**: Use consistent formatting and naming
|
||||
- **Keep it focused**: Each file should address a specific technology, framework, or use case
|
||||
- **Write clearly**: Use simple, direct language
|
||||
@@ -231,9 +311,9 @@ We welcome many kinds of contributions, including the custom categories below:
|
||||
| Category | Description | Emoji |
|
||||
| --- | --- | :---: |
|
||||
| **Instructions** | Custom instruction sets that guide GitHub Copilot behavior | 🧭 |
|
||||
| **Prompts** | Reusable or one-off prompts for GitHub Copilot | ⌨️ |
|
||||
| **Agents** | Defined GitHub Copilot roles or personalities | 🎭 |
|
||||
| **Skills** | Specialized knowledge of a task for GitHub Copilot | 🧰 |
|
||||
| **Workflows** | Agentic Workflows for AI-powered repository automation | ⚡ |
|
||||
| **Plugins** | Installable packages of related prompts, agents, or skills | 🎁 |
|
||||
|
||||
In addition, all standard contribution types supported by [All Contributors](https://allcontributors.org/emoji-key/) are recognized.
|
||||
@@ -243,7 +323,7 @@ In addition, all standard contribution types supported by [All Contributors](htt
|
||||
|
||||
## Code of Conduct
|
||||
|
||||
Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
|
||||
Please note that this project is maintained with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
|
||||
|
||||
## License
|
||||
|
||||
|
||||
141
README.md
141
README.md
@@ -2,34 +2,34 @@
|
||||
[](https://aka.ms/awesome-github-copilot) [](#contributors-)
|
||||
|
||||
|
||||
A community created collection of custom agents, prompts, and instructions to supercharge your GitHub Copilot experience across different domains, languages, and use cases.
|
||||
A community created collection of custom agents and instructions to supercharge your GitHub Copilot experience across different domains, languages, and use cases.
|
||||
|
||||
## 🚀 What is Awesome GitHub Copilot?
|
||||
|
||||
This repository provides a comprehensive toolkit for enhancing GitHub Copilot with specialized:
|
||||
|
||||
- **👉 [Awesome Agents](docs/README.agents.md)** - Specialized GitHub Copilot agents that integrate with MCP servers to provide enhanced capabilities for specific workflows and tools
|
||||
- **👉 [Awesome Prompts](docs/README.prompts.md)** - Focused, task-specific prompts for generating code, documentation, and solving specific problems
|
||||
- **👉 [Awesome Instructions](docs/README.instructions.md)** - Comprehensive coding standards and best practices that apply to specific file patterns or entire projects
|
||||
- **👉 [Awesome Hooks](docs/README.hooks.md)** - Automated workflows triggered by specific events during development, testing, and deployment
|
||||
- **👉 [Awesome Agentic Workflows](docs/README.workflows.md)** - AI-powered repository automations that run coding agents in GitHub Actions with natural language instructions
|
||||
- **👉 [Awesome Skills](docs/README.skills.md)** - Self-contained folders with instructions and bundled resources that enhance AI capabilities for specialized tasks
|
||||
- **👉 [Awesome Plugins](docs/README.plugins.md)** - Curated plugins of related prompts, agents, and skills organized around specific themes and workflows
|
||||
- **👉 [Awesome Plugins](docs/README.plugins.md)** - Curated plugins of related agents and skills organized around specific themes and workflows
|
||||
- **👉 [Awesome Cookbook Recipes](cookbook/README.md)** - Practical, copy-paste-ready code snippets and real-world examples for working with GitHub Copilot tools and features
|
||||
|
||||
## 🌟 Featured Plugins
|
||||
|
||||
Discover our curated plugins of prompts, agents, and skills organized around specific themes and workflows.
|
||||
Discover our curated plugins of agents and skills organized around specific themes and workflows.
|
||||
|
||||
| Name | Description | Items | Tags |
|
||||
| ---- | ----------- | ----- | ---- |
|
||||
| [Awesome Copilot](plugins/awesome-copilot/README.md) | Meta prompts that help you discover and generate curated GitHub Copilot agents, collections, instructions, prompts, and skills. | 5 items | github-copilot, discovery, meta, prompt-engineering, agents |
|
||||
| [Awesome Copilot](plugins/awesome-copilot/README.md) | Meta skills that help you discover and generate curated GitHub Copilot agents, collections, instructions, and skills. | 5 items | github-copilot, discovery, meta, prompt-engineering, agents |
|
||||
| [Copilot SDK](plugins/copilot-sdk/README.md) | Build applications with the GitHub Copilot SDK across multiple programming languages. Includes comprehensive instructions for C#, Go, Node.js/TypeScript, and Python to help you create AI-powered applications. | 5 items | copilot-sdk, sdk, csharp, go, nodejs, typescript, python, ai, github-copilot |
|
||||
| [Partners](plugins/partners/README.md) | Custom agents that have been created by GitHub partners | 20 items | devops, security, database, cloud, infrastructure, observability, feature-flags, cicd, migration, performance |
|
||||
|
||||
|
||||
## How to Install Customizations
|
||||
|
||||
To make it easy to add these customizations to your editor, we have created an [MCP Server](https://developer.microsoft.com/blog/announcing-awesome-copilot-mcp-server) that provides a prompt for searching and installing prompts, instructions, agents, and skills directly from this repository. You'll need to have Docker installed and running to run the MCP server locally.
|
||||
To make it easy to add these customizations to your editor, we have created an [MCP Server](https://developer.microsoft.com/blog/announcing-awesome-copilot-mcp-server) that provides functionality for searching and installing instructions, agents, and skills directly from this repository. You'll need to have Docker installed and running to run the MCP server locally.
|
||||
|
||||
[](https://aka.ms/awesome-copilot/mcp/vscode) [](https://aka.ms/awesome-copilot/mcp/vscode-insiders) [](https://aka.ms/awesome-copilot/mcp/vs)
|
||||
|
||||
@@ -57,13 +57,13 @@ To make it easy to add these customizations to your editor, we have created an [
|
||||
|
||||
## 📄 llms.txt
|
||||
|
||||
An [`llms.txt`](https://github.github.io/awesome-copilot/llms.txt) file following the [llmstxt.org](https://llmstxt.org/) specification is available on the GitHub Pages site. This machine-readable file makes it easy for Large Language Models to discover and understand all available agents, prompts, instructions, and skills, providing a structured overview of the repository's resources with names and descriptions.
|
||||
An [`llms.txt`](https://github.github.io/awesome-copilot/llms.txt) file following the [llmstxt.org](https://llmstxt.org/) specification is available on the GitHub Pages site. This machine-readable file makes it easy for Large Language Models to discover and understand all available agents, instructions, and skills, providing a structured overview of the repository's resources with names and descriptions.
|
||||
|
||||
## 🔧 How to Use
|
||||
|
||||
### 🔌 Plugins
|
||||
|
||||
Plugins are installable packages that bundle related agents, commands (prompts), and skills, making it easy to install a curated set of resources.
|
||||
Plugins are installable packages that bundle related agents and skills, making it easy to install a curated set of resources.
|
||||
|
||||
#### Installing Plugins
|
||||
|
||||
@@ -85,13 +85,9 @@ Alternatively, you can use the `/plugin` command within a Copilot chat session t
|
||||
|
||||
Custom agents can be used in Copilot coding agent (CCA), VS Code, and Copilot CLI (coming soon). For CCA, when assigning an issue to Copilot, select the custom agent from the provided list. In VS Code, you can activate the custom agent in the agents session, alongside built-in agents like Plan and Agent.
|
||||
|
||||
### 🎯 Prompts
|
||||
### 🎯 Skills
|
||||
|
||||
Use the `/` command in GitHub Copilot Chat to access prompts:
|
||||
|
||||
```plaintext
|
||||
/awesome-copilot create-readme
|
||||
```
|
||||
Skills are self-contained folders with instructions and bundled resources that enhance AI capabilities for specialized tasks. They can be accessed through the GitHub Copilot interface or installed via plugins.
|
||||
|
||||
### 📋 Instructions
|
||||
|
||||
@@ -101,9 +97,13 @@ Instructions automatically apply to files based on their patterns and provide co
|
||||
|
||||
Hooks enable automated workflows triggered by specific events during GitHub Copilot coding agent sessions (like sessionStart, sessionEnd, userPromptSubmitted). They can automate tasks like logging, auto-committing changes, or integrating with external services.
|
||||
|
||||
### ⚡ Agentic Workflows
|
||||
|
||||
[Agentic Workflows](https://github.github.com/gh-aw) are AI-powered repository automations that run coding agents in GitHub Actions. Defined in markdown with natural language instructions, they enable event-triggered and scheduled automation — from issue triage to daily reports.
|
||||
|
||||
## 🎯 Why Use Awesome GitHub Copilot?
|
||||
|
||||
- **Productivity**: Pre-built agents, prompts and instructions save time and provide consistent results.
|
||||
- **Productivity**: Pre-built agents and instructions save time and provide consistent results.
|
||||
- **Best Practices**: Benefit from community-curated coding standards and patterns.
|
||||
- **Specialized Assistance**: Access expert-level guidance through specialized custom agents.
|
||||
- **Continuous Learning**: Stay updated with the latest patterns and practices across technologies.
|
||||
@@ -112,7 +112,7 @@ Hooks enable automated workflows triggered by specific events during GitHub Copi
|
||||
|
||||
We welcome contributions! Please see our [Contributing Guidelines](CONTRIBUTING.md) for details on how to:
|
||||
|
||||
- Add new prompts, instructions, hooks, agents, or skills
|
||||
- Add new instructions, hooks, workflows, agents, or skills
|
||||
- Improve existing content
|
||||
- Report issues or suggest enhancements
|
||||
|
||||
@@ -128,9 +128,10 @@ For AI coding agents working with this project, refer to [AGENTS.md](AGENTS.md)
|
||||
## 📖 Repository Structure
|
||||
|
||||
```plaintext
|
||||
├── prompts/ # Task-specific prompts (.prompt.md)
|
||||
├── instructions/ # Coding standards and best practices (.instructions.md)
|
||||
├── agents/ # AI personas and specialized modes (.agent.md)
|
||||
├── hooks/ # Automated hooks for Copilot coding agent sessions
|
||||
├── workflows/ # Agentic Workflows for GitHub Actions automation
|
||||
├── plugins/ # Installable plugins bundling related items
|
||||
├── scripts/ # Utility scripts for maintenance
|
||||
└── skills/ # AI capabilities for specialized tasks
|
||||
@@ -152,7 +153,7 @@ The customizations in this repository are sourced from and created by third-part
|
||||
|
||||
---
|
||||
|
||||
**Ready to supercharge your coding experience?** Start exploring our [prompts](docs/README.prompts.md), [instructions](docs/README.instructions.md), [hooks](docs/README.hooks.md), and [custom agents](docs/README.agents.md)!
|
||||
**Ready to supercharge your coding experience?** Start exploring our [instructions](docs/README.instructions.md), [hooks](docs/README.hooks.md), [skills](docs/README.skills.md), [agentic workflows](docs/README.workflows.md), and [custom agents](docs/README.agents.md)!
|
||||
|
||||
## Contributors ✨
|
||||
|
||||
@@ -164,12 +165,12 @@ Thanks goes to these wonderful people ([emoji key](./CONTRIBUTING.md#contributor
|
||||
<table>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.aaron-powell.com/"><img src="https://avatars.githubusercontent.com/u/434140?v=4?s=100" width="100px;" alt="Aaron Powell"/><br /><sub><b>Aaron Powell</b></sub></a><br /><a href="#agents-aaronpowell" title="Specialized agents for GitHub Copilot">🎭</a> <a href="https://github.com/github/awesome-copilot/commits?author=aaronpowell" title="Code">💻</a> <a href="#plugins-aaronpowell" title="Curated plugins of related content">🎁</a> <a href="https://github.com/github/awesome-copilot/commits?author=aaronpowell" title="Documentation">📖</a> <a href="#infra-aaronpowell" title="Infrastructure (Hosting, Build-Tools, etc)">🚇</a> <a href="#instructions-aaronpowell" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#maintenance-aaronpowell" title="Maintenance">🚧</a> <a href="#prompts-aaronpowell" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.aaron-powell.com/"><img src="https://avatars.githubusercontent.com/u/434140?v=4?s=100" width="100px;" alt="Aaron Powell"/><br /><sub><b>Aaron Powell</b></sub></a><br /><a href="#agents-aaronpowell" title="Specialized agents for GitHub Copilot">🎭</a> <a href="https://github.com/github/awesome-copilot/commits?author=aaronpowell" title="Code">💻</a> <a href="#plugins-aaronpowell" title="Curated plugins for GitHub Copilot">🎁</a> <a href="https://github.com/github/awesome-copilot/commits?author=aaronpowell" title="Documentation">📖</a> <a href="#infra-aaronpowell" title="Infrastructure (Hosting, Build-Tools, etc)">🚇</a> <a href="#instructions-aaronpowell" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#maintenance-aaronpowell" title="Maintenance">🚧</a> <a href="#prompts-aaronpowell" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://codemilltech.com/"><img src="https://avatars.githubusercontent.com/u/2053639?v=4?s=100" width="100px;" alt="Matt Soucoup"/><br /><sub><b>Matt Soucoup</b></sub></a><br /><a href="#infra-codemillmatt" title="Infrastructure (Hosting, Build-Tools, etc)">🚇</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.buymeacoffee.com/troystaylor"><img src="https://avatars.githubusercontent.com/u/44444967?v=4?s=100" width="100px;" alt="Troy Simeon Taylor"/><br /><sub><b>Troy Simeon Taylor</b></sub></a><br /><a href="#agents-troystaylor" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#plugins-troystaylor" title="Curated plugins of related content">🎁</a> <a href="#instructions-troystaylor" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-troystaylor" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.buymeacoffee.com/troystaylor"><img src="https://avatars.githubusercontent.com/u/44444967?v=4?s=100" width="100px;" alt="Troy Simeon Taylor"/><br /><sub><b>Troy Simeon Taylor</b></sub></a><br /><a href="#agents-troystaylor" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#plugins-troystaylor" title="Curated plugins for GitHub Copilot">🎁</a> <a href="#instructions-troystaylor" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-troystaylor" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/abbas133"><img src="https://avatars.githubusercontent.com/u/7757139?v=4?s=100" width="100px;" alt="Abbas"/><br /><sub><b>Abbas</b></sub></a><br /><a href="#agents-abbas133" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#instructions-abbas133" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://calva.io/"><img src="https://avatars.githubusercontent.com/u/30010?v=4?s=100" width="100px;" alt="Peter Strömberg"/><br /><sub><b>Peter Strömberg</b></sub></a><br /><a href="#agents-PEZ" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#plugins-PEZ" title="Curated plugins of related content">🎁</a> <a href="#instructions-PEZ" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-PEZ" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://danielscottraynsford.com/"><img src="https://avatars.githubusercontent.com/u/7589164?v=4?s=100" width="100px;" alt="Daniel Scott-Raynsford"/><br /><sub><b>Daniel Scott-Raynsford</b></sub></a><br /><a href="#agents-PlagueHO" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#plugins-PlagueHO" title="Curated plugins of related content">🎁</a> <a href="#instructions-PlagueHO" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-PlagueHO" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://calva.io/"><img src="https://avatars.githubusercontent.com/u/30010?v=4?s=100" width="100px;" alt="Peter Strömberg"/><br /><sub><b>Peter Strömberg</b></sub></a><br /><a href="#agents-PEZ" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#plugins-PEZ" title="Curated plugins for GitHub Copilot">🎁</a> <a href="#instructions-PEZ" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-PEZ" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://danielscottraynsford.com/"><img src="https://avatars.githubusercontent.com/u/7589164?v=4?s=100" width="100px;" alt="Daniel Scott-Raynsford"/><br /><sub><b>Daniel Scott-Raynsford</b></sub></a><br /><a href="#agents-PlagueHO" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#plugins-PlagueHO" title="Curated plugins for GitHub Copilot">🎁</a> <a href="#instructions-PlagueHO" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-PlagueHO" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/jhauga"><img src="https://avatars.githubusercontent.com/u/10998676?v=4?s=100" width="100px;" alt="John Haugabook"/><br /><sub><b>John Haugabook</b></sub></a><br /><a href="#instructions-jhauga" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-jhauga" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -177,41 +178,41 @@ Thanks goes to these wonderful people ([emoji key](./CONTRIBUTING.md#contributor
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://digitarald.de/"><img src="https://avatars.githubusercontent.com/u/8599?v=4?s=100" width="100px;" alt="Harald Kirschner"/><br /><sub><b>Harald Kirschner</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=digitarald" title="Code">💻</a> <a href="https://github.com/github/awesome-copilot/commits?author=digitarald" title="Documentation">📖</a> <a href="#maintenance-digitarald" title="Maintenance">🚧</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://mubaidr.js.org/"><img src="https://avatars.githubusercontent.com/u/2222702?v=4?s=100" width="100px;" alt="Muhammad Ubaid Raza"/><br /><sub><b>Muhammad Ubaid Raza</b></sub></a><br /><a href="#agents-mubaidr" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#instructions-mubaidr" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/tmeschter"><img src="https://avatars.githubusercontent.com/u/10506730?v=4?s=100" width="100px;" alt="Tom Meschter"/><br /><sub><b>Tom Meschter</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=tmeschter" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.aungmyokyaw.com/"><img src="https://avatars.githubusercontent.com/u/9404824?v=4?s=100" width="100px;" alt="Aung Myo Kyaw"/><br /><sub><b>Aung Myo Kyaw</b></sub></a><br /><a href="#agents-AungMyoKyaw" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#prompts-AungMyoKyaw" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.aungmyokyaw.com/"><img src="https://avatars.githubusercontent.com/u/9404824?v=4?s=100" width="100px;" alt="Aung Myo Kyaw"/><br /><sub><b>Aung Myo Kyaw</b></sub></a><br /><a href="#agents-AungMyoKyaw" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/JasonYeMSFT"><img src="https://avatars.githubusercontent.com/u/39359541?v=4?s=100" width="100px;" alt="JasonYeMSFT"/><br /><sub><b>JasonYeMSFT</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=JasonYeMSFT" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.linkedin.com/in/jrc356/"><img src="https://avatars.githubusercontent.com/u/37387479?v=4?s=100" width="100px;" alt="Jon Corbin"/><br /><sub><b>Jon Corbin</b></sub></a><br /><a href="#agents-Jrc356" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#prompts-Jrc356" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.linkedin.com/in/jrc356/"><img src="https://avatars.githubusercontent.com/u/37387479?v=4?s=100" width="100px;" alt="Jon Corbin"/><br /><sub><b>Jon Corbin</b></sub></a><br /><a href="#agents-Jrc356" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/troytaylor-msft"><img src="https://avatars.githubusercontent.com/u/248058374?v=4?s=100" width="100px;" alt="troytaylor-msft"/><br /><sub><b>troytaylor-msft</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=troytaylor-msft" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://delatorre.dev/"><img src="https://avatars.githubusercontent.com/u/38289677?v=4?s=100" width="100px;" alt="Emerson Delatorre"/><br /><sub><b>Emerson Delatorre</b></sub></a><br /><a href="#instructions-fazedordecodigo" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/burkeholland"><img src="https://avatars.githubusercontent.com/u/686963?v=4?s=100" width="100px;" alt="Burke Holland"/><br /><sub><b>Burke Holland</b></sub></a><br /><a href="#agents-burkeholland" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#infra-burkeholland" title="Infrastructure (Hosting, Build-Tools, etc)">🚇</a> <a href="#instructions-burkeholland" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-burkeholland" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://yaooqinn.github.io/"><img src="https://avatars.githubusercontent.com/u/8326978?v=4?s=100" width="100px;" alt="Kent Yao"/><br /><sub><b>Kent Yao</b></sub></a><br /><a href="#instructions-yaooqinn" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-yaooqinn" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.devprodlogs.com/"><img src="https://avatars.githubusercontent.com/u/51440732?v=4?s=100" width="100px;" alt="Daniel Meppiel"/><br /><sub><b>Daniel Meppiel</b></sub></a><br /><a href="#prompts-danielmeppiel" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/burkeholland"><img src="https://avatars.githubusercontent.com/u/686963?v=4?s=100" width="100px;" alt="Burke Holland"/><br /><sub><b>Burke Holland</b></sub></a><br /><a href="#agents-burkeholland" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#infra-burkeholland" title="Infrastructure (Hosting, Build-Tools, etc)">🚇</a> <a href="#instructions-burkeholland" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://yaooqinn.github.io/"><img src="https://avatars.githubusercontent.com/u/8326978?v=4?s=100" width="100px;" alt="Kent Yao"/><br /><sub><b>Kent Yao</b></sub></a><br /><a href="#instructions-yaooqinn" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.devprodlogs.com/"><img src="https://avatars.githubusercontent.com/u/51440732?v=4?s=100" width="100px;" alt="Daniel Meppiel"/><br /><sub><b>Daniel Meppiel</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/yeelam-gordon"><img src="https://avatars.githubusercontent.com/u/73506701?v=4?s=100" width="100px;" alt="Gordon Lam"/><br /><sub><b>Gordon Lam</b></sub></a><br /><a href="#instructions-yeelam-gordon" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.madskristensen.net/"><img src="https://avatars.githubusercontent.com/u/1258877?v=4?s=100" width="100px;" alt="Mads Kristensen"/><br /><sub><b>Mads Kristensen</b></sub></a><br /><a href="#instructions-madskristensen" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://ks6088ts.github.io/"><img src="https://avatars.githubusercontent.com/u/1254960?v=4?s=100" width="100px;" alt="Shinji Takenaka"/><br /><sub><b>Shinji Takenaka</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=ks6088ts" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/spectatora"><img src="https://avatars.githubusercontent.com/u/1385755?v=4?s=100" width="100px;" alt="spectatora"/><br /><sub><b>spectatora</b></sub></a><br /><a href="#agents-spectatora" title="Specialized agents for GitHub Copilot">🎭</a> <a href="https://github.com/github/awesome-copilot/commits?author=spectatora" title="Code">💻</a> <a href="#maintenance-spectatora" title="Maintenance">🚧</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/sinedied"><img src="https://avatars.githubusercontent.com/u/593151?v=4?s=100" width="100px;" alt="Yohan Lasorsa"/><br /><sub><b>Yohan Lasorsa</b></sub></a><br /><a href="#instructions-sinedied" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-sinedied" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/VamshiVerma"><img src="https://avatars.githubusercontent.com/u/21999324?v=4?s=100" width="100px;" alt="Vamshi Verma"/><br /><sub><b>Vamshi Verma</b></sub></a><br /><a href="#instructions-VamshiVerma" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-VamshiVerma" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://montemagno.com/"><img src="https://avatars.githubusercontent.com/u/1676321?v=4?s=100" width="100px;" alt="James Montemagno"/><br /><sub><b>James Montemagno</b></sub></a><br /><a href="#agents-jamesmontemagno" title="Specialized agents for GitHub Copilot">🎭</a> <a href="https://github.com/github/awesome-copilot/commits?author=jamesmontemagno" title="Documentation">📖</a> <a href="#instructions-jamesmontemagno" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-jamesmontemagno" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/sinedied"><img src="https://avatars.githubusercontent.com/u/593151?v=4?s=100" width="100px;" alt="Yohan Lasorsa"/><br /><sub><b>Yohan Lasorsa</b></sub></a><br /><a href="#instructions-sinedied" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/VamshiVerma"><img src="https://avatars.githubusercontent.com/u/21999324?v=4?s=100" width="100px;" alt="Vamshi Verma"/><br /><sub><b>Vamshi Verma</b></sub></a><br /><a href="#instructions-VamshiVerma" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://montemagno.com/"><img src="https://avatars.githubusercontent.com/u/1676321?v=4?s=100" width="100px;" alt="James Montemagno"/><br /><sub><b>James Montemagno</b></sub></a><br /><a href="#agents-jamesmontemagno" title="Specialized agents for GitHub Copilot">🎭</a> <a href="https://github.com/github/awesome-copilot/commits?author=jamesmontemagno" title="Documentation">📖</a> <a href="#instructions-jamesmontemagno" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://twitter.com/alefragnani"><img src="https://avatars.githubusercontent.com/u/3781424?v=4?s=100" width="100px;" alt="Alessandro Fragnani"/><br /><sub><b>Alessandro Fragnani</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=alefragnani" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.linkedin.com/in/ambilykk/"><img src="https://avatars.githubusercontent.com/u/10282550?v=4?s=100" width="100px;" alt="Ambily"/><br /><sub><b>Ambily</b></sub></a><br /><a href="#agents-ambilykk" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#instructions-ambilykk" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/krushideep"><img src="https://avatars.githubusercontent.com/u/174652083?v=4?s=100" width="100px;" alt="krushideep"/><br /><sub><b>krushideep</b></sub></a><br /><a href="#prompts-krushideep" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/krushideep"><img src="https://avatars.githubusercontent.com/u/174652083?v=4?s=100" width="100px;" alt="krushideep"/><br /><sub><b>krushideep</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/mihsoft"><img src="https://avatars.githubusercontent.com/u/53946345?v=4?s=100" width="100px;" alt="devopsfan"/><br /><sub><b>devopsfan</b></sub></a><br /><a href="#agents-mihsoft" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://tgrall.github.io/"><img src="https://avatars.githubusercontent.com/u/541250?v=4?s=100" width="100px;" alt="Tugdual Grall"/><br /><sub><b>Tugdual Grall</b></sub></a><br /><a href="#instructions-tgrall" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-tgrall" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://tgrall.github.io/"><img src="https://avatars.githubusercontent.com/u/541250?v=4?s=100" width="100px;" alt="Tugdual Grall"/><br /><sub><b>Tugdual Grall</b></sub></a><br /><a href="#instructions-tgrall" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.promptboost.dev/"><img src="https://avatars.githubusercontent.com/u/5461862?v=4?s=100" width="100px;" alt="Oren Me"/><br /><sub><b>Oren Me</b></sub></a><br /><a href="#agents-OrenMe" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#instructions-OrenMe" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/mjrousos"><img src="https://avatars.githubusercontent.com/u/10077254?v=4?s=100" width="100px;" alt="Mike Rousos"/><br /><sub><b>Mike Rousos</b></sub></a><br /><a href="#instructions-mjrousos" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-mjrousos" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/mjrousos"><img src="https://avatars.githubusercontent.com/u/10077254?v=4?s=100" width="100px;" alt="Mike Rousos"/><br /><sub><b>Mike Rousos</b></sub></a><br /><a href="#instructions-mjrousos" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://devkimchi.com/"><img src="https://avatars.githubusercontent.com/u/1538528?v=4?s=100" width="100px;" alt="Justin Yoo"/><br /><sub><b>Justin Yoo</b></sub></a><br /><a href="#instructions-justinyoo" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/guiopen"><img src="https://avatars.githubusercontent.com/u/94094527?v=4?s=100" width="100px;" alt="Guilherme do Amaral Alves "/><br /><sub><b>Guilherme do Amaral Alves </b></sub></a><br /><a href="#instructions-guiopen" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.linkedin.com/in/griffinashe/"><img src="https://avatars.githubusercontent.com/u/6391612?v=4?s=100" width="100px;" alt="Griffin Ashe"/><br /><sub><b>Griffin Ashe</b></sub></a><br /><a href="#agents-griffinashe" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#plugins-griffinashe" title="Curated plugins of related content">🎁</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.linkedin.com/in/griffinashe/"><img src="https://avatars.githubusercontent.com/u/6391612?v=4?s=100" width="100px;" alt="Griffin Ashe"/><br /><sub><b>Griffin Ashe</b></sub></a><br /><a href="#agents-griffinashe" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#plugins-griffinashe" title="Curated plugins for GitHub Copilot">🎁</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/anchildress1"><img src="https://avatars.githubusercontent.com/u/6563688?v=4?s=100" width="100px;" alt="Ashley Childress"/><br /><sub><b>Ashley Childress</b></sub></a><br /><a href="#agents-anchildress1" title="Specialized agents for GitHub Copilot">🎭</a> <a href="https://github.com/github/awesome-copilot/commits?author=anchildress1" title="Documentation">📖</a> <a href="#instructions-anchildress1" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#infra-anchildress1" title="Infrastructure (Hosting, Build-Tools, etc)">🚇</a> <a href="https://github.com/github/awesome-copilot/commits?author=anchildress1" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://www.senseof.tech/"><img src="https://avatars.githubusercontent.com/u/50712277?v=4?s=100" width="100px;" alt="Adrien Clerbois"/><br /><sub><b>Adrien Clerbois</b></sub></a><br /><a href="#agents-AClerbois" title="Specialized agents for GitHub Copilot">🎭</a> <a href="https://github.com/github/awesome-copilot/commits?author=AClerbois" title="Documentation">📖</a> <a href="#prompts-AClerbois" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://www.senseof.tech/"><img src="https://avatars.githubusercontent.com/u/50712277?v=4?s=100" width="100px;" alt="Adrien Clerbois"/><br /><sub><b>Adrien Clerbois</b></sub></a><br /><a href="#agents-AClerbois" title="Specialized agents for GitHub Copilot">🎭</a> <a href="https://github.com/github/awesome-copilot/commits?author=AClerbois" title="Documentation">📖</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/Vhivi"><img src="https://avatars.githubusercontent.com/u/38220028?v=4?s=100" width="100px;" alt="ANGELELLI David"/><br /><sub><b>ANGELELLI David</b></sub></a><br /><a href="#agents-Vhivi" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://markdav.is/"><img src="https://avatars.githubusercontent.com/u/311063?v=4?s=100" width="100px;" alt="Mark Davis"/><br /><sub><b>Mark Davis</b></sub></a><br /><a href="#instructions-markdav-is" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/MattVevang"><img src="https://avatars.githubusercontent.com/u/20714898?v=4?s=100" width="100px;" alt="Matt Vevang"/><br /><sub><b>Matt Vevang</b></sub></a><br /><a href="#instructions-MattVevang" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
@@ -219,19 +220,19 @@ Thanks goes to these wonderful people ([emoji key](./CONTRIBUTING.md#contributor
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/nullchimp"><img src="https://avatars.githubusercontent.com/u/58362593?v=4?s=100" width="100px;" alt="NULLchimp"/><br /><sub><b>NULLchimp</b></sub></a><br /><a href="#agents-nullchimp" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/pkarda"><img src="https://avatars.githubusercontent.com/u/12649718?v=4?s=100" width="100px;" alt="Peter Karda"/><br /><sub><b>Peter Karda</b></sub></a><br /><a href="#prompts-pkarda" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/sdolgin"><img src="https://avatars.githubusercontent.com/u/576449?v=4?s=100" width="100px;" alt="Saul Dolgin"/><br /><sub><b>Saul Dolgin</b></sub></a><br /><a href="#agents-sdolgin" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#instructions-sdolgin" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-sdolgin" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/shubham070"><img src="https://avatars.githubusercontent.com/u/5480589?v=4?s=100" width="100px;" alt="Shubham Gaikwad"/><br /><sub><b>Shubham Gaikwad</b></sub></a><br /><a href="#agents-shubham070" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#instructions-shubham070" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-shubham070" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/pkarda"><img src="https://avatars.githubusercontent.com/u/12649718?v=4?s=100" width="100px;" alt="Peter Karda"/><br /><sub><b>Peter Karda</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/sdolgin"><img src="https://avatars.githubusercontent.com/u/576449?v=4?s=100" width="100px;" alt="Saul Dolgin"/><br /><sub><b>Saul Dolgin</b></sub></a><br /><a href="#agents-sdolgin" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#instructions-sdolgin" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/shubham070"><img src="https://avatars.githubusercontent.com/u/5480589?v=4?s=100" width="100px;" alt="Shubham Gaikwad"/><br /><sub><b>Shubham Gaikwad</b></sub></a><br /><a href="#agents-shubham070" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#instructions-shubham070" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/TheovanKraay"><img src="https://avatars.githubusercontent.com/u/24420698?v=4?s=100" width="100px;" alt="Theo van Kraay"/><br /><sub><b>Theo van Kraay</b></sub></a><br /><a href="#instructions-TheovanKraay" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/TianqiZhang"><img src="https://avatars.githubusercontent.com/u/5326582?v=4?s=100" width="100px;" alt="Tianqi Zhang"/><br /><sub><b>Tianqi Zhang</b></sub></a><br /><a href="#agents-TianqiZhang" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://blog.miniasp.com/"><img src="https://avatars.githubusercontent.com/u/88981?v=4?s=100" width="100px;" alt="Will 保哥"/><br /><sub><b>Will 保哥</b></sub></a><br /><a href="#agents-doggy8088" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#prompts-doggy8088" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://blog.miniasp.com/"><img src="https://avatars.githubusercontent.com/u/88981?v=4?s=100" width="100px;" alt="Will 保哥"/><br /><sub><b>Will 保哥</b></sub></a><br /><a href="#agents-doggy8088" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://tsubalog.hatenablog.com/"><img src="https://avatars.githubusercontent.com/u/1592808?v=4?s=100" width="100px;" alt="Yuta Matsumura"/><br /><sub><b>Yuta Matsumura</b></sub></a><br /><a href="#instructions-tsubakimoto" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/anschnapp"><img src="https://avatars.githubusercontent.com/u/17565996?v=4?s=100" width="100px;" alt="anschnapp"/><br /><sub><b>anschnapp</b></sub></a><br /><a href="#agents-anschnapp" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/hizahizi-hizumi"><img src="https://avatars.githubusercontent.com/u/163728895?v=4?s=100" width="100px;" alt="hizahizi-hizumi"/><br /><sub><b>hizahizi-hizumi</b></sub></a><br /><a href="#instructions-hizahizi-hizumi" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://jianminhuang.cc/"><img src="https://avatars.githubusercontent.com/u/6296280?v=4?s=100" width="100px;" alt="黃健旻 Vincent Huang"/><br /><sub><b>黃健旻 Vincent Huang</b></sub></a><br /><a href="#prompts-Jian-Min-Huang" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://brunoborges.io/"><img src="https://avatars.githubusercontent.com/u/129743?v=4?s=100" width="100px;" alt="Bruno Borges"/><br /><sub><b>Bruno Borges</b></sub></a><br /><a href="#plugins-brunoborges" title="Curated plugins of related content">🎁</a> <a href="#instructions-brunoborges" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://brunoborges.io/"><img src="https://avatars.githubusercontent.com/u/129743?v=4?s=100" width="100px;" alt="Bruno Borges"/><br /><sub><b>Bruno Borges</b></sub></a><br /><a href="#plugins-brunoborges" title="Curated plugins for GitHub Copilot">🎁</a> <a href="#instructions-brunoborges" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.movinglive.ca/"><img src="https://avatars.githubusercontent.com/u/14792628?v=4?s=100" width="100px;" alt="Steve Magne"/><br /><sub><b>Steve Magne</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=MovingLive" title="Documentation">📖</a> <a href="#instructions-MovingLive" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://shaneneuville.com/"><img src="https://avatars.githubusercontent.com/u/5375137?v=4?s=100" width="100px;" alt="Shane Neuville"/><br /><sub><b>Shane Neuville</b></sub></a><br /><a href="#agents-PureWeen" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#instructions-PureWeen" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
</tr>
|
||||
@@ -246,11 +247,11 @@ Thanks goes to these wonderful people ([emoji key](./CONTRIBUTING.md#contributor
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://blog.codewithdan.com/"><img src="https://avatars.githubusercontent.com/u/1767249?v=4?s=100" width="100px;" alt="Dan Wahlin"/><br /><sub><b>Dan Wahlin</b></sub></a><br /><a href="#agents-DanWahlin" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://debbie.codes/"><img src="https://avatars.githubusercontent.com/u/13063165?v=4?s=100" width="100px;" alt="Debbie O'Brien"/><br /><sub><b>Debbie O'Brien</b></sub></a><br /><a href="#agents-debs-obrien" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#instructions-debs-obrien" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-debs-obrien" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/echarrod"><img src="https://avatars.githubusercontent.com/u/1381991?v=4?s=100" width="100px;" alt="Ed Harrod"/><br /><sub><b>Ed Harrod</b></sub></a><br /><a href="#prompts-echarrod" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://learn.microsoft.com/dotnet"><img src="https://avatars.githubusercontent.com/u/24882762?v=4?s=100" width="100px;" alt="Genevieve Warren"/><br /><sub><b>Genevieve Warren</b></sub></a><br /><a href="#prompts-gewarren" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/guigui42"><img src="https://avatars.githubusercontent.com/u/2376010?v=4?s=100" width="100px;" alt="Guillaume"/><br /><sub><b>Guillaume</b></sub></a><br /><a href="#agents-guigui42" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#prompts-guigui42" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/riqueufmg"><img src="https://avatars.githubusercontent.com/u/108551585?v=4?s=100" width="100px;" alt="Henrique Nunes"/><br /><sub><b>Henrique Nunes</b></sub></a><br /><a href="#prompts-riqueufmg" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://debbie.codes/"><img src="https://avatars.githubusercontent.com/u/13063165?v=4?s=100" width="100px;" alt="Debbie O'Brien"/><br /><sub><b>Debbie O'Brien</b></sub></a><br /><a href="#agents-debs-obrien" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#instructions-debs-obrien" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/echarrod"><img src="https://avatars.githubusercontent.com/u/1381991?v=4?s=100" width="100px;" alt="Ed Harrod"/><br /><sub><b>Ed Harrod</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://learn.microsoft.com/dotnet"><img src="https://avatars.githubusercontent.com/u/24882762?v=4?s=100" width="100px;" alt="Genevieve Warren"/><br /><sub><b>Genevieve Warren</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/guigui42"><img src="https://avatars.githubusercontent.com/u/2376010?v=4?s=100" width="100px;" alt="Guillaume"/><br /><sub><b>Guillaume</b></sub></a><br /><a href="#agents-guigui42" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/riqueufmg"><img src="https://avatars.githubusercontent.com/u/108551585?v=4?s=100" width="100px;" alt="Henrique Nunes"/><br /><sub><b>Henrique Nunes</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/jeremiah-snee-openx"><img src="https://avatars.githubusercontent.com/u/113928685?v=4?s=100" width="100px;" alt="Jeremiah Snee"/><br /><sub><b>Jeremiah Snee</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=jeremiah-snee-openx" title="Code">💻</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -268,23 +269,23 @@ Thanks goes to these wonderful people ([emoji key](./CONTRIBUTING.md#contributor
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://salih.guru/"><img src="https://avatars.githubusercontent.com/u/76786120?v=4?s=100" width="100px;" alt="Salih"/><br /><sub><b>Salih</b></sub></a><br /><a href="#instructions-salihguru" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://graef.io/"><img src="https://avatars.githubusercontent.com/u/19261257?v=4?s=100" width="100px;" alt="Sebastian Gräf"/><br /><sub><b>Sebastian Gräf</b></sub></a><br /><a href="#agents-segraef" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#instructions-segraef" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/SebastienDegodez"><img src="https://avatars.githubusercontent.com/u/2349146?v=4?s=100" width="100px;" alt="Sebastien DEGODEZ"/><br /><sub><b>Sebastien DEGODEZ</b></sub></a><br /><a href="#instructions-SebastienDegodez" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/sesmyrnov"><img src="https://avatars.githubusercontent.com/u/59627981?v=4?s=100" width="100px;" alt="Sergiy Smyrnov"/><br /><sub><b>Sergiy Smyrnov</b></sub></a><br /><a href="#prompts-sesmyrnov" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/sesmyrnov"><img src="https://avatars.githubusercontent.com/u/59627981?v=4?s=100" width="100px;" alt="Sergiy Smyrnov"/><br /><sub><b>Sergiy Smyrnov</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/SomeSolutionsArchitect"><img src="https://avatars.githubusercontent.com/u/139817767?v=4?s=100" width="100px;" alt="SomeSolutionsArchitect"/><br /><sub><b>SomeSolutionsArchitect</b></sub></a><br /><a href="#agents-SomeSolutionsArchitect" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/kewalaka"><img src="https://avatars.githubusercontent.com/u/3146590?v=4?s=100" width="100px;" alt="Stu Mace"/><br /><sub><b>Stu Mace</b></sub></a><br /><a href="#agents-kewalaka" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#plugins-kewalaka" title="Curated plugins of related content">🎁</a> <a href="#instructions-kewalaka" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/kewalaka"><img src="https://avatars.githubusercontent.com/u/3146590?v=4?s=100" width="100px;" alt="Stu Mace"/><br /><sub><b>Stu Mace</b></sub></a><br /><a href="#agents-kewalaka" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#plugins-kewalaka" title="Curated plugins for GitHub Copilot">🎁</a> <a href="#instructions-kewalaka" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/STRUDSO"><img src="https://avatars.githubusercontent.com/u/1543732?v=4?s=100" width="100px;" alt="Søren Trudsø Mahon"/><br /><sub><b>Søren Trudsø Mahon</b></sub></a><br /><a href="#instructions-STRUDSO" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://enakdesign.com/"><img src="https://avatars.githubusercontent.com/u/14024037?v=4?s=100" width="100px;" alt="Tj Vita"/><br /><sub><b>Tj Vita</b></sub></a><br /><a href="#agents-semperteneo" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/pelikhan"><img src="https://avatars.githubusercontent.com/u/4175913?v=4?s=100" width="100px;" alt="Peli de Halleux"/><br /><sub><b>Peli de Halleux</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=pelikhan" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.paulomorgado.net/"><img src="https://avatars.githubusercontent.com/u/470455?v=4?s=100" width="100px;" alt="Paulo Morgado"/><br /><sub><b>Paulo Morgado</b></sub></a><br /><a href="#prompts-paulomorgado" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.paulomorgado.net/"><img src="https://avatars.githubusercontent.com/u/470455?v=4?s=100" width="100px;" alt="Paulo Morgado"/><br /><sub><b>Paulo Morgado</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://paul.crane.net.nz/"><img src="https://avatars.githubusercontent.com/u/808676?v=4?s=100" width="100px;" alt="Paul Crane"/><br /><sub><b>Paul Crane</b></sub></a><br /><a href="#agents-pcrane" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.pamelafox.org/"><img src="https://avatars.githubusercontent.com/u/297042?v=4?s=100" width="100px;" alt="Pamela Fox"/><br /><sub><b>Pamela Fox</b></sub></a><br /><a href="#prompts-pamelafox" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.pamelafox.org/"><img src="https://avatars.githubusercontent.com/u/297042?v=4?s=100" width="100px;" alt="Pamela Fox"/><br /><sub><b>Pamela Fox</b></sub></a><br /></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://oskarthornblad.se/"><img src="https://avatars.githubusercontent.com/u/640102?v=4?s=100" width="100px;" alt="Oskar Thornblad"/><br /><sub><b>Oskar Thornblad</b></sub></a><br /><a href="#instructions-prewk" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/nischays"><img src="https://avatars.githubusercontent.com/u/54121853?v=4?s=100" width="100px;" alt="Nischay Sharma"/><br /><sub><b>Nischay Sharma</b></sub></a><br /><a href="#agents-nischays" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/Naikabg"><img src="https://avatars.githubusercontent.com/u/19915620?v=4?s=100" width="100px;" alt="Nikolay Marinov"/><br /><sub><b>Nikolay Marinov</b></sub></a><br /><a href="#agents-Naikabg" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.linkedin.com/in/niksac"><img src="https://avatars.githubusercontent.com/u/20246918?v=4?s=100" width="100px;" alt="Nik Sachdeva"/><br /><sub><b>Nik Sachdeva</b></sub></a><br /><a href="#agents-niksacdev" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#plugins-niksacdev" title="Curated plugins of related content">🎁</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.linkedin.com/in/niksac"><img src="https://avatars.githubusercontent.com/u/20246918?v=4?s=100" width="100px;" alt="Nik Sachdeva"/><br /><sub><b>Nik Sachdeva</b></sub></a><br /><a href="#agents-niksacdev" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#plugins-niksacdev" title="Curated plugins for GitHub Copilot">🎁</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://onetipaweek.com/"><img src="https://avatars.githubusercontent.com/u/833231?v=4?s=100" width="100px;" alt="Nick Taylor"/><br /><sub><b>Nick Taylor</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=nickytonline" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://nicholasdbrady.github.io/cookbook/"><img src="https://avatars.githubusercontent.com/u/18353756?v=4?s=100" width="100px;" alt="Nick Brady"/><br /><sub><b>Nick Brady</b></sub></a><br /><a href="#agents-nicholasdbrady" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/nastanford"><img src="https://avatars.githubusercontent.com/u/1755947?v=4?s=100" width="100px;" alt="Nathan Stanford Sr"/><br /><sub><b>Nathan Stanford Sr</b></sub></a><br /><a href="#instructions-nastanford" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
@@ -292,10 +293,10 @@ Thanks goes to these wonderful people ([emoji key](./CONTRIBUTING.md#contributor
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/matebarabas"><img src="https://avatars.githubusercontent.com/u/22733424?v=4?s=100" width="100px;" alt="Máté Barabás"/><br /><sub><b>Máté Barabás</b></sub></a><br /><a href="#instructions-matebarabas" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/mikeparker104"><img src="https://avatars.githubusercontent.com/u/12763221?v=4?s=100" width="100px;" alt="Mike Parker"/><br /><sub><b>Mike Parker</b></sub></a><br /><a href="#instructions-mikeparker104" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/mikekistler"><img src="https://avatars.githubusercontent.com/u/85643503?v=4?s=100" width="100px;" alt="Mike Kistler"/><br /><sub><b>Mike Kistler</b></sub></a><br /><a href="#prompts-mikekistler" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/mikekistler"><img src="https://avatars.githubusercontent.com/u/85643503?v=4?s=100" width="100px;" alt="Mike Kistler"/><br /><sub><b>Mike Kistler</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/giomartinsdev"><img src="https://avatars.githubusercontent.com/u/125399281?v=4?s=100" width="100px;" alt="Giovanni de Almeida Martins"/><br /><sub><b>Giovanni de Almeida Martins</b></sub></a><br /><a href="#instructions-giomartinsdev" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/dgh06175"><img src="https://avatars.githubusercontent.com/u/77305722?v=4?s=100" width="100px;" alt="이상현"/><br /><sub><b>이상현</b></sub></a><br /><a href="#instructions-dgh06175" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/zooav"><img src="https://avatars.githubusercontent.com/u/12625412?v=4?s=100" width="100px;" alt="Ankur Sharma"/><br /><sub><b>Ankur Sharma</b></sub></a><br /><a href="#prompts-zooav" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/zooav"><img src="https://avatars.githubusercontent.com/u/12625412?v=4?s=100" width="100px;" alt="Ankur Sharma"/><br /><sub><b>Ankur Sharma</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/webreidi"><img src="https://avatars.githubusercontent.com/u/55603905?v=4?s=100" width="100px;" alt="Wendy Breiding"/><br /><sub><b>Wendy Breiding</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=webreidi" title="Code">💻</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -303,9 +304,9 @@ Thanks goes to these wonderful people ([emoji key](./CONTRIBUTING.md#contributor
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://about.me/shane-lee"><img src="https://avatars.githubusercontent.com/u/5466825?v=4?s=100" width="100px;" alt="shane lee"/><br /><sub><b>shane lee</b></sub></a><br /><a href="#instructions-shavo007" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/sdanzo-hrb"><img src="https://avatars.githubusercontent.com/u/136493100?v=4?s=100" width="100px;" alt="sdanzo-hrb"/><br /><sub><b>sdanzo-hrb</b></sub></a><br /><a href="#agents-sdanzo-hrb" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/nativebpm"><img src="https://avatars.githubusercontent.com/u/33398121?v=4?s=100" width="100px;" alt="sauran"/><br /><sub><b>sauran</b></sub></a><br /><a href="#instructions-isauran" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/samqbush"><img src="https://avatars.githubusercontent.com/u/74389839?v=4?s=100" width="100px;" alt="samqbush"/><br /><sub><b>samqbush</b></sub></a><br /><a href="#prompts-samqbush" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/samqbush"><img src="https://avatars.githubusercontent.com/u/74389839?v=4?s=100" width="100px;" alt="samqbush"/><br /><sub><b>samqbush</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/pareenaverma"><img src="https://avatars.githubusercontent.com/u/59843121?v=4?s=100" width="100px;" alt="pareenaverma"/><br /><sub><b>pareenaverma</b></sub></a><br /><a href="#agents-pareenaverma" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/oleksiyyurchyna"><img src="https://avatars.githubusercontent.com/u/10256765?v=4?s=100" width="100px;" alt="oleksiyyurchyna"/><br /><sub><b>oleksiyyurchyna</b></sub></a><br /><a href="#plugins-oleksiyyurchyna" title="Curated plugins of related content">🎁</a> <a href="#prompts-oleksiyyurchyna" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/oleksiyyurchyna"><img src="https://avatars.githubusercontent.com/u/10256765?v=4?s=100" width="100px;" alt="oleksiyyurchyna"/><br /><sub><b>oleksiyyurchyna</b></sub></a><br /><a href="#plugins-oleksiyyurchyna" title="Curated plugins for GitHub Copilot">🎁</a> <a href="#prompts-oleksiyyurchyna" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/time-by-waves"><img src="https://avatars.githubusercontent.com/u/34587654?v=4?s=100" width="100px;" alt="oceans-of-time"/><br /><sub><b>oceans-of-time</b></sub></a><br /><a href="#instructions-time-by-waves" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
@@ -314,7 +315,7 @@ Thanks goes to these wonderful people ([emoji key](./CONTRIBUTING.md#contributor
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/factory-davidgu"><img src="https://avatars.githubusercontent.com/u/229352262?v=4?s=100" width="100px;" alt="factory-davidgu"/><br /><sub><b>factory-davidgu</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=factory-davidgu" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/dangelov-qa"><img src="https://avatars.githubusercontent.com/u/92313553?v=4?s=100" width="100px;" alt="dangelov-qa"/><br /><sub><b>dangelov-qa</b></sub></a><br /><a href="#agents-dangelov-qa" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/BenoitMaucotel"><img src="https://avatars.githubusercontent.com/u/54392431?v=4?s=100" width="100px;" alt="BenoitMaucotel"/><br /><sub><b>BenoitMaucotel</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=BenoitMaucotel" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/benjisho-aidome"><img src="https://avatars.githubusercontent.com/u/218995725?v=4?s=100" width="100px;" alt="benjisho-aidome"/><br /><sub><b>benjisho-aidome</b></sub></a><br /><a href="#agents-benjisho-aidome" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#instructions-benjisho-aidome" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-benjisho-aidome" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/benjisho-aidome"><img src="https://avatars.githubusercontent.com/u/218995725?v=4?s=100" width="100px;" alt="benjisho-aidome"/><br /><sub><b>benjisho-aidome</b></sub></a><br /><a href="#agents-benjisho-aidome" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#instructions-benjisho-aidome" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/yukiomoto"><img src="https://avatars.githubusercontent.com/u/38450410?v=4?s=100" width="100px;" alt="Yuki Omoto"/><br /><sub><b>Yuki Omoto</b></sub></a><br /><a href="#instructions-yukiomoto" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
@@ -327,26 +328,26 @@ Thanks goes to these wonderful people ([emoji key](./CONTRIBUTING.md#contributor
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://tinyurl.com/3p5j9mwe"><img src="https://avatars.githubusercontent.com/u/9591887?v=4?s=100" width="100px;" alt="Udaya Veeramreddygari"/><br /><sub><b>Udaya Veeramreddygari</b></sub></a><br /><a href="#instructions-udayakumarreddyv" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/iletai"><img src="https://avatars.githubusercontent.com/u/26614687?v=4?s=100" width="100px;" alt="Tài Lê"/><br /><sub><b>Tài Lê</b></sub></a><br /><a href="#prompts-iletai" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/iletai"><img src="https://avatars.githubusercontent.com/u/26614687?v=4?s=100" width="100px;" alt="Tài Lê"/><br /><sub><b>Tài Lê</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://tsubasaogawa.me/"><img src="https://avatars.githubusercontent.com/u/7788821?v=4?s=100" width="100px;" alt="Tsubasa Ogawa"/><br /><sub><b>Tsubasa Ogawa</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=tsubasaogawa" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://glsauto.com/"><img src="https://avatars.githubusercontent.com/u/132710946?v=4?s=100" width="100px;" alt="Troy Witthoeft (glsauto)"/><br /><sub><b>Troy Witthoeft (glsauto)</b></sub></a><br /><a href="#instructions-twitthoeft-gls" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://jfversluis.dev/"><img src="https://avatars.githubusercontent.com/u/939291?v=4?s=100" width="100px;" alt="Gerald Versluis"/><br /><sub><b>Gerald Versluis</b></sub></a><br /><a href="#instructions-jfversluis" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/geoder101"><img src="https://avatars.githubusercontent.com/u/145904?v=4?s=100" width="100px;" alt="George Dernikos"/><br /><sub><b>George Dernikos</b></sub></a><br /><a href="#prompts-geoder101" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/geoder101"><img src="https://avatars.githubusercontent.com/u/145904?v=4?s=100" width="100px;" alt="George Dernikos"/><br /><sub><b>George Dernikos</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/gautambaghel"><img src="https://avatars.githubusercontent.com/u/22324290?v=4?s=100" width="100px;" alt="Gautam"/><br /><sub><b>Gautam</b></sub></a><br /><a href="#agents-gautambaghel" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/feapaydin"><img src="https://avatars.githubusercontent.com/u/19946639?v=4?s=100" width="100px;" alt="Furkan Enes"/><br /><sub><b>Furkan Enes</b></sub></a><br /><a href="#instructions-feapaydin" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/fmuecke"><img src="https://avatars.githubusercontent.com/u/7921024?v=4?s=100" width="100px;" alt="Florian Mücke"/><br /><sub><b>Florian Mücke</b></sub></a><br /><a href="#agents-fmuecke" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.felixarjuna.dev/"><img src="https://avatars.githubusercontent.com/u/79026094?v=4?s=100" width="100px;" alt="Felix Arjuna"/><br /><sub><b>Felix Arjuna</b></sub></a><br /><a href="#instructions-felixarjuna" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/ewega"><img src="https://avatars.githubusercontent.com/u/26189114?v=4?s=100" width="100px;" alt="Eldrick Wega"/><br /><sub><b>Eldrick Wega</b></sub></a><br /><a href="#prompts-ewega" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/danchev"><img src="https://avatars.githubusercontent.com/u/12420863?v=4?s=100" width="100px;" alt="Dobri Danchev"/><br /><sub><b>Dobri Danchev</b></sub></a><br /><a href="#prompts-danchev" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://dgamboa.com/"><img src="https://avatars.githubusercontent.com/u/7052267?v=4?s=100" width="100px;" alt="Diego Gamboa"/><br /><sub><b>Diego Gamboa</b></sub></a><br /><a href="#prompts-difegam" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/derekclair"><img src="https://avatars.githubusercontent.com/u/5247629?v=4?s=100" width="100px;" alt="Derek Clair"/><br /><sub><b>Derek Clair</b></sub></a><br /><a href="#agents-derekclair" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#prompts-derekclair" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/ewega"><img src="https://avatars.githubusercontent.com/u/26189114?v=4?s=100" width="100px;" alt="Eldrick Wega"/><br /><sub><b>Eldrick Wega</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/danchev"><img src="https://avatars.githubusercontent.com/u/12420863?v=4?s=100" width="100px;" alt="Dobri Danchev"/><br /><sub><b>Dobri Danchev</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://dgamboa.com/"><img src="https://avatars.githubusercontent.com/u/7052267?v=4?s=100" width="100px;" alt="Diego Gamboa"/><br /><sub><b>Diego Gamboa</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/derekclair"><img src="https://avatars.githubusercontent.com/u/5247629?v=4?s=100" width="100px;" alt="Derek Clair"/><br /><sub><b>Derek Clair</b></sub></a><br /><a href="#agents-derekclair" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://dev.to/davidortinau"><img src="https://avatars.githubusercontent.com/u/41873?v=4?s=100" width="100px;" alt="David Ortinau"/><br /><sub><b>David Ortinau</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=davidortinau" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/danielabbatt"><img src="https://avatars.githubusercontent.com/u/8926756?v=4?s=100" width="100px;" alt="Daniel Abbatt"/><br /><sub><b>Daniel Abbatt</b></sub></a><br /><a href="#instructions-danielabbatt" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/CypherHK"><img src="https://avatars.githubusercontent.com/u/230935834?v=4?s=100" width="100px;" alt="CypherHK"/><br /><sub><b>CypherHK</b></sub></a><br /><a href="#agents-CypherHK" title="Specialized agents for GitHub Copilot">🎭</a> <a href="#prompts-CypherHK" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/CypherHK"><img src="https://avatars.githubusercontent.com/u/230935834?v=4?s=100" width="100px;" alt="CypherHK"/><br /><sub><b>CypherHK</b></sub></a><br /><a href="#agents-CypherHK" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/craigbekker"><img src="https://avatars.githubusercontent.com/u/1115912?v=4?s=100" width="100px;" alt="Craig Bekker"/><br /><sub><b>Craig Bekker</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=craigbekker" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.peug.net/"><img src="https://avatars.githubusercontent.com/u/3845786?v=4?s=100" width="100px;" alt="Christophe Peugnet"/><br /><sub><b>Christophe Peugnet</b></sub></a><br /><a href="#instructions-tossnet" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/lechnerc77"><img src="https://avatars.githubusercontent.com/u/22294087?v=4?s=100" width="100px;" alt="Christian Lechner"/><br /><sub><b>Christian Lechner</b></sub></a><br /><a href="#instructions-lechnerc77" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
@@ -354,7 +355,7 @@ Thanks goes to these wonderful people ([emoji key](./CONTRIBUTING.md#contributor
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/artemsaveliev"><img src="https://avatars.githubusercontent.com/u/15679218?v=4?s=100" width="100px;" alt="Artem Saveliev"/><br /><sub><b>Artem Saveliev</b></sub></a><br /><a href="#instructions-artemsaveliev" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://javaetmoi.com/"><img src="https://avatars.githubusercontent.com/u/838318?v=4?s=100" width="100px;" alt="Antoine Rey"/><br /><sub><b>Antoine Rey</b></sub></a><br /><a href="#prompts-arey" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://javaetmoi.com/"><img src="https://avatars.githubusercontent.com/u/838318?v=4?s=100" width="100px;" alt="Antoine Rey"/><br /><sub><b>Antoine Rey</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/PiKa919"><img src="https://avatars.githubusercontent.com/u/96786190?v=4?s=100" width="100px;" alt="Ankit Das"/><br /><sub><b>Ankit Das</b></sub></a><br /><a href="#instructions-PiKa919" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/alineavila"><img src="https://avatars.githubusercontent.com/u/24813256?v=4?s=100" width="100px;" alt="Aline Ávila"/><br /><sub><b>Aline Ávila</b></sub></a><br /><a href="#instructions-alineavila" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/martin-cod"><img src="https://avatars.githubusercontent.com/u/33550246?v=4?s=100" width="100px;" alt="Alexander Martinkevich"/><br /><sub><b>Alexander Martinkevich</b></sub></a><br /><a href="#agents-martin-cod" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
@@ -368,7 +369,7 @@ Thanks goes to these wonderful people ([emoji key](./CONTRIBUTING.md#contributor
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/4regab"><img src="https://avatars.githubusercontent.com/u/178603515?v=4?s=100" width="100px;" alt="4regab"/><br /><sub><b>4regab</b></sub></a><br /><a href="#instructions-4regab" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/MiguelElGallo"><img src="https://avatars.githubusercontent.com/u/60221874?v=4?s=100" width="100px;" alt="Miguel P Z"/><br /><sub><b>Miguel P Z</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=MiguelElGallo" title="Documentation">📖</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://a11ysupport.io/"><img src="https://avatars.githubusercontent.com/u/498678?v=4?s=100" width="100px;" alt="Michael Fairchild"/><br /><sub><b>Michael Fairchild</b></sub></a><br /><a href="#instructions-mfairchild365" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.linkedin.com/in/michael-volz/"><img src="https://avatars.githubusercontent.com/u/129928?v=4?s=100" width="100px;" alt="Michael A. Volz (Flynn)"/><br /><sub><b>Michael A. Volz (Flynn)</b></sub></a><br /><a href="#prompts-michaelvolz" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.linkedin.com/in/michael-volz/"><img src="https://avatars.githubusercontent.com/u/129928?v=4?s=100" width="100px;" alt="Michael A. Volz (Flynn)"/><br /><sub><b>Michael A. Volz (Flynn)</b></sub></a><br /></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/Mike-Hanna"><img src="https://avatars.githubusercontent.com/u/50142889?v=4?s=100" width="100px;" alt="Michael"/><br /><sub><b>Michael</b></sub></a><br /><a href="#instructions-Mike-Hanna" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
@@ -385,27 +386,31 @@ Thanks goes to these wonderful people ([emoji key](./CONTRIBUTING.md#contributor
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/whiteken"><img src="https://avatars.githubusercontent.com/u/20211937?v=4?s=100" width="100px;" alt="Kenny White"/><br /><sub><b>Kenny White</b></sub></a><br /><a href="#instructions-whiteken" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/KaloyanGenev"><img src="https://avatars.githubusercontent.com/u/42644424?v=4?s=100" width="100px;" alt="KaloyanGenev"/><br /><sub><b>KaloyanGenev</b></sub></a><br /><a href="#agents-KaloyanGenev" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/Ranrar"><img src="https://avatars.githubusercontent.com/u/95967772?v=4?s=100" width="100px;" alt="Kim Skov Rasmussen"/><br /><sub><b>Kim Skov Rasmussen</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=Ranrar" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.julien-dubois.com/"><img src="https://avatars.githubusercontent.com/u/316835?v=4?s=100" width="100px;" alt="Julien Dubois"/><br /><sub><b>Julien Dubois</b></sub></a><br /><a href="#prompts-jdubois" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.julien-dubois.com/"><img src="https://avatars.githubusercontent.com/u/316835?v=4?s=100" width="100px;" alt="Julien Dubois"/><br /><sub><b>Julien Dubois</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://digio.es/"><img src="https://avatars.githubusercontent.com/u/173672918?v=4?s=100" width="100px;" alt="José Antonio Garrido"/><br /><sub><b>José Antonio Garrido</b></sub></a><br /><a href="#instructions-josegarridodigio" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://www.sugbo4j.co.nz/"><img src="https://avatars.githubusercontent.com/u/15100839?v=4?s=100" width="100px;" alt="Joseph Gonzales"/><br /><sub><b>Joseph Gonzales</b></sub></a><br /><a href="#instructions-josephgonzales01" title="Custom instructions for GitHub Copilot">🧭</a> <a href="#prompts-josephgonzales01" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://www.sugbo4j.co.nz/"><img src="https://avatars.githubusercontent.com/u/15100839?v=4?s=100" width="100px;" alt="Joseph Gonzales"/><br /><sub><b>Joseph Gonzales</b></sub></a><br /><a href="#instructions-josephgonzales01" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/yortch"><img src="https://avatars.githubusercontent.com/u/4576246?v=4?s=100" width="100px;" alt="Jorge Balderas"/><br /><sub><b>Jorge Balderas</b></sub></a><br /><a href="#instructions-yortch" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://johnpapa.net/"><img src="https://avatars.githubusercontent.com/u/1202528?v=4?s=100" width="100px;" alt="John Papa"/><br /><sub><b>John Papa</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=johnpapa" title="Code">💻</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://www.johnlokerse.dev/"><img src="https://avatars.githubusercontent.com/u/3514513?v=4?s=100" width="100px;" alt="John"/><br /><sub><b>John</b></sub></a><br /><a href="#agents-johnlokerse" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="http://joe-watkins.io/"><img src="https://avatars.githubusercontent.com/u/3695795?v=4?s=100" width="100px;" alt="Joe Watkins"/><br /><sub><b>Joe Watkins</b></sub></a><br /><a href="#instructions-joe-watkins" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://jan-v.nl/"><img src="https://avatars.githubusercontent.com/u/462356?v=4?s=100" width="100px;" alt="Jan de Vries"/><br /><sub><b>Jan de Vries</b></sub></a><br /><a href="#agents-Jandev" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/nohwnd"><img src="https://avatars.githubusercontent.com/u/5735905?v=4?s=100" width="100px;" alt="Jakub Jareš"/><br /><sub><b>Jakub Jareš</b></sub></a><br /><a href="#prompts-nohwnd" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/nohwnd"><img src="https://avatars.githubusercontent.com/u/5735905?v=4?s=100" width="100px;" alt="Jakub Jareš"/><br /><sub><b>Jakub Jareš</b></sub></a><br /></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/jaxn"><img src="https://avatars.githubusercontent.com/u/29095?v=4?s=100" width="100px;" alt="Jackson Miller"/><br /><sub><b>Jackson Miller</b></sub></a><br /><a href="#instructions-jaxn" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/Ioana37"><img src="https://avatars.githubusercontent.com/u/69301842?v=4?s=100" width="100px;" alt="Ioana A"/><br /><sub><b>Ioana A</b></sub></a><br /><a href="#instructions-Ioana37" title="Custom instructions for GitHub Copilot">🧭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/hunterhogan"><img src="https://avatars.githubusercontent.com/u/2958419?v=4?s=100" width="100px;" alt="Hunter Hogan"/><br /><sub><b>Hunter Hogan</b></sub></a><br /><a href="#agents-hunterhogan" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/hashimwarren"><img src="https://avatars.githubusercontent.com/u/6027587?v=4?s=100" width="100px;" alt="Hashim Warren"/><br /><sub><b>Hashim Warren</b></sub></a><br /><a href="#agents-hashimwarren" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/Arggon"><img src="https://avatars.githubusercontent.com/u/20962238?v=4?s=100" width="100px;" alt="Gonzalo"/><br /><sub><b>Gonzalo</b></sub></a><br /><a href="#prompts-Arggon" title="Reusable prompts for GitHub Copilot">⌨️</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/Arggon"><img src="https://avatars.githubusercontent.com/u/20962238?v=4?s=100" width="100px;" alt="Gonzalo"/><br /><sub><b>Gonzalo</b></sub></a><br /></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://hachyderm.io/@0gis0"><img src="https://avatars.githubusercontent.com/u/175379?v=4?s=100" width="100px;" alt="Gisela Torres"/><br /><sub><b>Gisela Torres</b></sub></a><br /><a href="#agents-0GiS0" title="Specialized agents for GitHub Copilot">🎭</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/shibicr93"><img src="https://avatars.githubusercontent.com/u/6803434?v=4?s=100" width="100px;" alt="Shibi Ramachandran"/><br /><sub><b>Shibi Ramachandran</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=shibicr93" title="Code">💻</a></td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/lupritz"><img src="https://avatars.githubusercontent.com/u/145381941?v=4?s=100" width="100px;" alt="lupritz"/><br /><sub><b>lupritz</b></sub></a><br /><a href="#plugin-lupritz" title="Plugin/utility libraries">🔌</a></td>
|
||||
<td align="center" valign="top" width="14.28%"><a href="https://github.com/bhect0"><img src="https://avatars.githubusercontent.com/u/96436904?v=4?s=100" width="100px;" alt="Héctor Benedicte"/><br /><sub><b>Héctor Benedicte</b></sub></a><br /><a href="https://github.com/github/awesome-copilot/commits?author=bhect0" title="Code">💻</a></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
<tfoot>
|
||||
<tr>
|
||||
|
||||
@@ -1,5 +1,3 @@
|
||||
Thanks for helping make GitHub safe for everyone.
|
||||
|
||||
# Security
|
||||
|
||||
GitHub takes the security of our software products and services seriously, including all of the open source code repositories managed through our GitHub organizations, such as [GitHub](https://github.com/GitHub).
|
||||
|
||||
@@ -14,17 +14,17 @@ Browser Tester: UI/UX testing, visual verification, browser automation
|
||||
Browser automation, UI/UX and Accessibility (WCAG) auditing, Performance profiling and console log analysis, End-to-end verification and visual regression, Multi-tab/Frame management and Advanced State Injection
|
||||
</expertise>
|
||||
|
||||
<mission>
|
||||
Browser automation, Validation Matrix scenarios, visual verification via screenshots
|
||||
</mission>
|
||||
|
||||
<workflow>
|
||||
- Analyze: Identify plan_id, task_def. Use reference_cache for WCAG standards. Map validation_matrix to scenarios.
|
||||
- Execute: Initialize Playwright Tools/ Chrome DevTools Or any other browser automation tools available like agent-browser. Follow Observation-First loop (Navigate → Snapshot → Action). Verify UI state after each. Capture evidence.
|
||||
- Verify: Check console/network, run task_block.verification, review against AC.
|
||||
- Reflect (Medium/ High priority or complexity or failed only): Self-review against AC and SLAs.
|
||||
- Cleanup: close browser sessions.
|
||||
- Return simple JSON: {"status": "success|failed|needs_revision", "task_id": "[task_id]", "summary": "[brief summary]"}
|
||||
- Initialize: Identify plan_id, task_def. Map scenarios.
|
||||
- Execute: Run scenarios iteratively using available browser tools. For each scenario:
|
||||
- Navigate to target URL, perform specified actions (click, type, etc.) using preferred browser tools.
|
||||
- After each scenario, verify outcomes against expected results.
|
||||
- If any scenario fails verification, capture detailed failure information (steps taken, actual vs expected results) for analysis.
|
||||
- Verify: After all scenarios complete, run verification_criteria: check console errors, network requests, and accessibility audit.
|
||||
- Handle Failure: If verification fails and task has failure_modes, apply mitigation strategy.
|
||||
- Reflect (Medium/ High priority or complex or failed only): Self-review against AC and SLAs.
|
||||
- Cleanup: Close browser sessions.
|
||||
- Return JSON per <output_format_guide>
|
||||
</workflow>
|
||||
|
||||
<operating_rules>
|
||||
@@ -32,15 +32,75 @@ Browser automation, Validation Matrix scenarios, visual verification via screens
|
||||
- Built-in preferred; batch independent calls
|
||||
- Think-Before-Action: Validate logic and simulate expected outcomes via an internal <thought> block before any tool execution or final response; verify pathing, dependencies, and constraints to ensure "one-shot" success.
|
||||
- Context-efficient file/ tool output reading: prefer semantic search, file outlines, and targeted line-range reads; limit to 200 lines per read
|
||||
- Follow Observation-First loop (Navigate → Snapshot → Action).
|
||||
- Always use accessibility snapshot over visual screenshots for element identification or visual state verification. Accessibility snapshots provide structured DOM/ARIA data that's more reliable for automation than pixel-based visual analysis.
|
||||
- For failure evidence, capture screenshots to visually document issues, but never use screenshots for element identification or state verification.
|
||||
- Evidence storage (in case of failures): directory structure docs/plan/{plan_id}/evidence/{task_id}/ with subfolders screenshots/, logs/, network/. Files named by timestamp and scenario.
|
||||
- Use UIDs from take_snapshot; avoid raw CSS/XPath
|
||||
- Never navigate to production without approval
|
||||
- Never navigate to production without approval.
|
||||
- Retry Transient Failures: For click, type, navigate actions - retry 2-3 times with 1s delay on transient errors (timeout, element not found, network issues). Escalate after max retries.
|
||||
- Errors: transient→handle, persistent→escalate
|
||||
- Memory: Use memory create/update when discovering architectural decisions, integration patterns, or code conventions.
|
||||
|
||||
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
|
||||
</operating_rules>
|
||||
|
||||
<input_format_guide>
|
||||
```yaml
|
||||
task_id: string
|
||||
plan_id: string
|
||||
plan_path: string # "docs/plan/{plan_id}/plan.yaml"
|
||||
task_definition: object # Full task from plan.yaml
|
||||
# Includes: validation_matrix, browser_tool_preference, etc.
|
||||
```
|
||||
</input_format_guide>
|
||||
|
||||
<reflection_memory>
|
||||
- Learn from execution, user guidance, decisions, patterns
|
||||
- Complete → Store discoveries → Next: Read & apply
|
||||
</reflection_memory>
|
||||
|
||||
<verification_criteria>
|
||||
- step: "Run validation matrix scenarios"
|
||||
pass_condition: "All scenarios pass expected_result, UI state matches expectations"
|
||||
fail_action: "Report failing scenarios with details (steps taken, actual result, expected result)"
|
||||
|
||||
- step: "Check console errors"
|
||||
pass_condition: "No console errors or warnings"
|
||||
fail_action: "Capture console errors with stack traces, timestamps, and reproduction steps to evidence/logs/"
|
||||
|
||||
- step: "Check network requests"
|
||||
pass_condition: "No network failures (4xx/5xx errors), all requests complete successfully"
|
||||
fail_action: "Capture network failures with request details, error responses, and timestamps to evidence/network/"
|
||||
|
||||
- step: "Accessibility audit (WCAG compliance)"
|
||||
pass_condition: "No accessibility violations (keyboard navigation, ARIA labels, color contrast)"
|
||||
fail_action: "Document accessibility violations with WCAG guideline references"
|
||||
</verification_criteria>
|
||||
|
||||
<output_format_guide>
|
||||
```json
|
||||
{
|
||||
"status": "success|failed|needs_revision",
|
||||
"task_id": "[task_id]",
|
||||
"plan_id": "[plan_id]",
|
||||
"summary": "[brief summary ≤3 sentences]",
|
||||
"extra": {
|
||||
"console_errors": 0,
|
||||
"network_failures": 0,
|
||||
"accessibility_issues": 0,
|
||||
"evidence_path": "docs/plan/{plan_id}/evidence/{task_id}/",
|
||||
"failures": [
|
||||
{
|
||||
"criteria": "console_errors|network_requests|accessibility|validation_matrix",
|
||||
"details": "Description of failure with specific errors",
|
||||
"scenario": "Scenario name if applicable"
|
||||
}
|
||||
]
|
||||
}
|
||||
}
|
||||
```
|
||||
</output_format_guide>
|
||||
|
||||
<final_anchor>
|
||||
Test UI/UX, validate matrix; return simple JSON {status, task_id, summary}; autonomous, no user interaction; stay as chrome-tester.
|
||||
Test UI/UX, validate matrix; return JSON per <output_format_guide>; autonomous, no user interaction; stay as browser-tester.
|
||||
</final_anchor>
|
||||
</agent>
|
||||
|
||||
@@ -18,10 +18,11 @@ Containerization (Docker) and Orchestration (K8s), CI/CD pipeline design and aut
|
||||
- Preflight: Verify environment (docker, kubectl), permissions, resources. Ensure idempotency.
|
||||
- Approval Check: If task.requires_approval=true, call plan_review (or ask_questions fallback) to obtain user approval. If denied, return status=needs_revision and abort.
|
||||
- Execute: Run infrastructure operations using idempotent commands. Use atomic operations.
|
||||
- Verify: Run task_block.verification and health checks. Verify state matches expected.
|
||||
- Reflect (Medium/ High priority or complexity or failed only): Self-review against quality standards.
|
||||
- Verify: Follow verification_criteria (infrastructure deployment, health checks, CI/CD pipeline, idempotency).
|
||||
- Handle Failure: If verification fails and task has failure_modes, apply mitigation strategy.
|
||||
- Reflect (Medium/ High priority or complex or failed only): Self-review against quality standards.
|
||||
- Cleanup: Remove orphaned resources, close connections.
|
||||
- Return simple JSON: {"status": "success|failed|needs_revision", "task_id": "[task_id]", "summary": "[brief summary]"}
|
||||
- Return JSON per <output_format_guide>
|
||||
</workflow>
|
||||
|
||||
<operating_rules>
|
||||
@@ -31,7 +32,7 @@ Containerization (Docker) and Orchestration (K8s), CI/CD pipeline design and aut
|
||||
- Context-efficient file/ tool output reading: prefer semantic search, file outlines, and targeted line-range reads; limit to 200 lines per read
|
||||
- Always run health checks after operations; verify against expected state
|
||||
- Errors: transient→handle, persistent→escalate
|
||||
- Memory: Use memory create/update when discovering architectural decisions, integration patterns, or code conventions.
|
||||
|
||||
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
|
||||
</operating_rules>
|
||||
|
||||
@@ -47,7 +48,56 @@ Conditions: task.environment = 'production' AND operation involves deploying to
|
||||
Action: Call plan_review to confirm production deployment. If denied, abort and return status=needs_revision.
|
||||
</approval_gates>
|
||||
|
||||
<input_format_guide>
|
||||
```yaml
|
||||
task_id: string
|
||||
plan_id: string
|
||||
plan_path: string # "docs/plan/{plan_id}/plan.yaml"
|
||||
task_definition: object # Full task from plan.yaml
|
||||
# Includes: environment, requires_approval, security_sensitive, etc.
|
||||
```
|
||||
</input_format_guide>
|
||||
|
||||
<reflection_memory>
|
||||
- Learn from execution, user guidance, decisions, patterns
|
||||
- Complete → Store discoveries → Next: Read & apply
|
||||
</reflection_memory>
|
||||
|
||||
<verification_criteria>
|
||||
- step: "Verify infrastructure deployment"
|
||||
pass_condition: "Services running, logs clean, no errors in deployment"
|
||||
fail_action: "Check logs, identify root cause, rollback if needed"
|
||||
|
||||
- step: "Run health checks"
|
||||
pass_condition: "All health checks pass, state matches expected configuration"
|
||||
fail_action: "Document failing health checks, investigate, apply fixes"
|
||||
|
||||
- step: "Verify CI/CD pipeline"
|
||||
pass_condition: "Pipeline completes successfully, all stages pass"
|
||||
fail_action: "Fix pipeline configuration, re-run pipeline"
|
||||
|
||||
- step: "Verify idempotency"
|
||||
pass_condition: "Re-running operations produces same result (no side effects)"
|
||||
fail_action: "Document non-idempotent operations, fix to ensure idempotency"
|
||||
</verification_criteria>
|
||||
|
||||
<output_format_guide>
|
||||
```json
|
||||
{
|
||||
"status": "success|failed|needs_revision",
|
||||
"task_id": "[task_id]",
|
||||
"plan_id": "[plan_id]",
|
||||
"summary": "[brief summary ≤3 sentences]",
|
||||
"extra": {
|
||||
"health_checks": {},
|
||||
"resource_usage": {},
|
||||
"deployment_details": {}
|
||||
}
|
||||
}
|
||||
```
|
||||
</output_format_guide>
|
||||
|
||||
<final_anchor>
|
||||
Execute container/CI/CD ops, verify health, prevent secrets; return simple JSON {status, task_id, summary}; autonomous except production approval gates; stay as devops.
|
||||
Execute container/CI/CD ops, verify health, prevent secrets; return JSON per <output_format_guide>; autonomous except production approval gates; stay as devops.
|
||||
</final_anchor>
|
||||
</agent>
|
||||
|
||||
@@ -17,10 +17,11 @@ Technical communication and documentation architecture, API specification (OpenA
|
||||
<workflow>
|
||||
- Analyze: Identify scope/audience from task_def. Research standards/parity. Create coverage matrix.
|
||||
- Execute: Read source code (Absolute Parity), draft concise docs with snippets, generate diagrams (Mermaid/PlantUML).
|
||||
- Verify: Run task_block.verification, check get_errors (compile/lint).
|
||||
* For updates: verify parity on delta only (get_changed_files)
|
||||
- Verify: Follow verification_criteria (completeness, accuracy, formatting, get_errors).
|
||||
* For updates: verify parity on delta only
|
||||
* For new features: verify documentation completeness against source code and acceptance_criteria
|
||||
- Return simple JSON: {"status": "success|failed|needs_revision", "task_id": "[task_id]", "summary": "[brief summary]"}
|
||||
- Reflect (Medium/High priority or complexity or failed only): Self-review for completeness, accuracy, and bias.
|
||||
- Return JSON per <output_format_guide>
|
||||
</workflow>
|
||||
|
||||
<operating_rules>
|
||||
@@ -34,11 +35,60 @@ Technical communication and documentation architecture, API specification (OpenA
|
||||
- Verify parity: on delta for updates; against source code for new features
|
||||
- Never use TBD/TODO as final documentation
|
||||
- Handle errors: transient→handle, persistent→escalate
|
||||
- Memory: Use memory create/update when discovering architectural decisions, integration patterns, or code conventions.
|
||||
|
||||
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
|
||||
</operating_rules>
|
||||
|
||||
<input_format_guide>
|
||||
```yaml
|
||||
task_id: string
|
||||
plan_id: string
|
||||
plan_path: string # "docs/plan/{plan_id}/plan.yaml"
|
||||
task_definition: object # Full task from plan.yaml
|
||||
# Includes: audience, coverage_matrix, is_update, etc.
|
||||
```
|
||||
</input_format_guide>
|
||||
|
||||
<reflection_memory>
|
||||
- Learn from execution, user guidance, decisions, patterns
|
||||
- Complete → Store discoveries → Next: Read & apply
|
||||
</reflection_memory>
|
||||
|
||||
<verification_criteria>
|
||||
- step: "Verify documentation completeness"
|
||||
pass_condition: "All items in coverage_matrix documented, no TBD/TODO placeholders"
|
||||
fail_action: "Add missing documentation, replace TBD/TODO with actual content"
|
||||
|
||||
- step: "Verify accuracy (parity with source code)"
|
||||
pass_condition: "Documentation matches implementation (APIs, parameters, return values)"
|
||||
fail_action: "Update documentation to match actual source code"
|
||||
|
||||
- step: "Verify formatting and structure"
|
||||
pass_condition: "Proper Markdown/HTML formatting, diagrams render correctly, no broken links"
|
||||
fail_action: "Fix formatting issues, ensure diagrams render, fix broken links"
|
||||
|
||||
- step: "Check get_errors (compile/lint)"
|
||||
pass_condition: "No errors or warnings in documentation files"
|
||||
fail_action: "Fix all errors and warnings"
|
||||
</verification_criteria>
|
||||
|
||||
<output_format_guide>
|
||||
```json
|
||||
{
|
||||
"status": "success|failed|needs_revision",
|
||||
"task_id": "[task_id]",
|
||||
"plan_id": "[plan_id]",
|
||||
"summary": "[brief summary ≤3 sentences]",
|
||||
"extra": {
|
||||
"docs_created": [],
|
||||
"docs_updated": [],
|
||||
"parity_verified": true
|
||||
}
|
||||
}
|
||||
```
|
||||
</output_format_guide>
|
||||
|
||||
<final_anchor>
|
||||
Return simple JSON {status, task_id, summary} with parity verified; docs-only; autonomous, no user interaction; stay as documentation-writer.
|
||||
Return JSON per <output_format_guide> with parity verified; docs-only; autonomous, no user interaction; stay as documentation-writer.
|
||||
</final_anchor>
|
||||
</agent>
|
||||
|
||||
@@ -11,15 +11,18 @@ Code Implementer: executes architectural vision, solves implementation details,
|
||||
</role>
|
||||
|
||||
<expertise>
|
||||
Full-stack implementation and refactoring, Unit and integration testing (TDD/VDD), Debugging and Root Cause Analysis, Performance optimization and code hygiene, Modular architecture and small-file organization, Minimal/concise/lint-compatible code, YAGNI/KISS/DRY principles, Functional programming
|
||||
Full-stack implementation and refactoring, Unit and integration testing (TDD/VDD), Debugging and Root Cause Analysis, Performance optimization and code hygiene, Modular architecture and small-file organization
|
||||
</expertise>
|
||||
|
||||
<workflow>
|
||||
- TDD Red: Write failing tests FIRST, confirm they FAIL.
|
||||
- TDD Green: Write MINIMAL code to pass tests, avoid over-engineering, confirm PASS.
|
||||
- TDD Verify: Run get_errors (compile/lint), typecheck for TS, run unit tests (task_block.verification).
|
||||
- Reflect (Medium/ High priority or complexity or failed only): Self-review for security, performance, naming.
|
||||
- Return simple JSON: {"status": "success|failed|needs_revision", "task_id": "[task_id]", "summary": "[brief summary]"}
|
||||
- Analyze: Parse plan_id, objective. Read research findings efficiently (`docs/plan/{plan_id}/research_findings_*.yaml`) to extract relevant insights for planning.
|
||||
- Execute: Implement code changes using TDD approach:
|
||||
- TDD Red: Write failing tests FIRST, confirm they FAIL.
|
||||
- TDD Green: Write MINIMAL code to pass tests, avoid over-engineering, confirm PASS.
|
||||
- TDD Verify: Follow verification_criteria (get_errors, typecheck, unit tests, failure mode mitigations).
|
||||
- Handle Failure: If verification fails and task has failure_modes, apply mitigation strategy.
|
||||
- Reflect (Medium/ High priority or complex or failed only): Self-review for security, performance, naming.
|
||||
- Return JSON per <output_format_guide>
|
||||
</workflow>
|
||||
|
||||
<operating_rules>
|
||||
@@ -28,7 +31,14 @@ Full-stack implementation and refactoring, Unit and integration testing (TDD/VDD
|
||||
- Think-Before-Action: Validate logic and simulate expected outcomes via an internal <thought> block before any tool execution or final response; verify pathing, dependencies, and constraints to ensure "one-shot" success.
|
||||
- Context-efficient file/ tool output reading: prefer semantic search, file outlines, and targeted line-range reads; limit to 200 lines per read
|
||||
- Adhere to tech_stack; no unapproved libraries
|
||||
- Tes writing guidleines:
|
||||
- CRITICAL: Code Quality Enforcement - MUST follow these principles:
|
||||
* YAGNI (You Aren't Gonna Need It)
|
||||
* KISS (Keep It Simple, Stupid)
|
||||
* DRY (Don't Repeat Yourself)
|
||||
* Functional Programming
|
||||
* Avoid over-engineering
|
||||
* Lint Compatibility
|
||||
- Test writing guidelines:
|
||||
- Don't write tests for what the type system already guarantees.
|
||||
- Test behaviour not implementation details; avoid brittle tests
|
||||
- Only use methods available on the interface to verify behavior; avoid test-only hooks or exposing internals
|
||||
@@ -37,11 +47,59 @@ Full-stack implementation and refactoring, Unit and integration testing (TDD/VDD
|
||||
- Security issues → fix immediately or escalate
|
||||
- Test failures → fix all or escalate
|
||||
- Vulnerabilities → fix before handoff
|
||||
- Memory: Use memory create/update when discovering architectural decisions, integration patterns, or code conventions.
|
||||
|
||||
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
|
||||
</operating_rules>
|
||||
|
||||
<input_format_guide>
|
||||
```yaml
|
||||
task_id: string
|
||||
plan_id: string
|
||||
plan_path: string # "docs/plan/{plan_id}/plan.yaml"
|
||||
task_definition: object # Full task from plan.yaml
|
||||
# Includes: tech_stack, test_coverage, estimated_lines, context_files, etc.
|
||||
```
|
||||
</input_format_guide>
|
||||
|
||||
<reflection_memory>
|
||||
- Learn from execution, user guidance, decisions, patterns
|
||||
- Complete → Store discoveries → Next: Read & apply
|
||||
</reflection_memory>
|
||||
|
||||
<verification_criteria>
|
||||
- step: "Run get_errors (compile/lint)"
|
||||
pass_condition: "No errors or warnings"
|
||||
fail_action: "Fix all errors and warnings before proceeding"
|
||||
|
||||
- step: "Run typecheck for TypeScript"
|
||||
pass_condition: "No type errors"
|
||||
fail_action: "Fix all type errors"
|
||||
|
||||
- step: "Run unit tests"
|
||||
pass_condition: "All tests pass"
|
||||
fail_action: "Fix all failing tests"
|
||||
|
||||
- step: "Apply failure mode mitigations (if needed)"
|
||||
pass_condition: "Mitigation strategy resolves the issue"
|
||||
fail_action: "Report to orchestrator for escalation if mitigation fails"
|
||||
</verification_criteria>
|
||||
|
||||
<output_format_guide>
|
||||
```json
|
||||
{
|
||||
"status": "success|failed|needs_revision",
|
||||
"task_id": "[task_id]",
|
||||
"plan_id": "[plan_id]",
|
||||
"summary": "[brief summary ≤3 sentences]",
|
||||
"extra": {
|
||||
"execution_details": {},
|
||||
"test_results": {}
|
||||
}
|
||||
}
|
||||
```
|
||||
</output_format_guide>
|
||||
|
||||
<final_anchor>
|
||||
Implement TDD code, pass tests, verify quality; return simple JSON {status, task_id, summary}; autonomous, no user interaction; stay as implementer.
|
||||
Implement TDD code, pass tests, verify quality; ENFORCE YAGNI/KISS/DRY/SOLID principles (YAGNI/KISS take precedence over SOLID); return JSON per <output_format_guide>; autonomous, no user interaction; stay as implementer.
|
||||
</final_anchor>
|
||||
</agent>
|
||||
|
||||
@@ -27,20 +27,19 @@ gem-researcher, gem-planner, gem-implementer, gem-browser-tester, gem-devops, ge
|
||||
- Phase 1: Research (if no research findings):
|
||||
- Parse user request, generate plan_id with unique identifier and date
|
||||
- Identify key domains/features/directories (focus_areas) from request
|
||||
- Delegate to multiple `gem-researcher` instances concurrent (one per focus_area) with: objective, focus_area, plan_id
|
||||
- Wait for all researchers to complete
|
||||
- Delegate to multiple `gem-researcher` instances concurrent (one per focus_area):
|
||||
* Pass: plan_id, objective, focus_area per <delegation_protocol>
|
||||
- On researcher failure: retry same focus_area (max 2 retries), then proceed with available findings
|
||||
- Phase 2: Planning:
|
||||
- Verify research findings exist in `docs/plan/{plan_id}/research_findings_*.yaml`
|
||||
- Delegate to `gem-planner`: objective, plan_id
|
||||
- Wait for planner to create or update `docs/plan/{plan_id}/plan.yaml`
|
||||
- Delegate to `gem-planner`: Pass plan_id, objective, research_findings_paths per <delegation_protocol>
|
||||
- Phase 3: Execution Loop:
|
||||
- Check for user feedback: If user provides new objective/changes, route to Phase 2 (Planning) with updated objective.
|
||||
- Read `plan.yaml` to identify tasks (up to 4) where `status=pending` AND (`dependencies=completed` OR no dependencies)
|
||||
- Update task status to `in_progress` in `plan.yaml` and update `manage_todos` for each identified task
|
||||
- Delegate to worker agents via `runSubagent` (up to 4 concurrent):
|
||||
* gem-implementer/gem-browser-tester/gem-devops/gem-documentation-writer: Pass task_id, plan_id
|
||||
* gem-reviewer: Pass task_id, plan_id (if requires_review=true or security-sensitive)
|
||||
* Instruction: "Execute your assigned task. Return JSON with status, task_id, and summary only."
|
||||
- Wait for all agents to complete
|
||||
* Prepare delegation params: base_params + agent_specific_params per <delegation_protocol>
|
||||
* gem-implementer/gem-browser-tester/gem-devops/gem-documentation-writer: Pass full delegation params
|
||||
* gem-reviewer: Pass full delegation params (if requires_review=true or security-sensitive)
|
||||
* Instruction: "Execute your assigned task. Return JSON per your <output_format_guide>."
|
||||
- Synthesize: Update `plan.yaml` status based on results:
|
||||
* SUCCESS → Mark task completed
|
||||
* FAILURE/NEEDS_REVISION → If fixable: delegate to `gem-implementer` (task_id, plan_id); If requires replanning: delegate to `gem-planner` (objective, plan_id)
|
||||
@@ -48,30 +47,84 @@ gem-researcher, gem-planner, gem-implementer, gem-browser-tester, gem-devops, ge
|
||||
- Phase 4: Completion (all tasks completed):
|
||||
- Validate all tasks marked completed in `plan.yaml`
|
||||
- If any pending/in_progress: identify blockers, delegate to `gem-planner` for resolution
|
||||
- FINAL: Present comprehensive summary via `walkthrough_review`
|
||||
* If userfeedback indicates changes needed → Route updated objective, plan_id to `gem-researcher` (for findings changes) or `gem-planner` (for plan changes)
|
||||
- FINAL: Create walkthrough document file (non-blocking) with comprehensive summary
|
||||
* File: `docs/plan/{plan_id}/walkthrough-completion-{timestamp}.md`
|
||||
* Content: Overview, tasks completed, outcomes, next steps
|
||||
* If user feedback indicates changes needed → Route updated objective, plan_id to `gem-researcher` (for findings changes) or `gem-planner` (for plan changes)
|
||||
</workflow>
|
||||
|
||||
<delegation_protocol>
|
||||
base_params:
|
||||
- task_id: string
|
||||
- plan_id: string
|
||||
- plan_path: string # "docs/plan/{plan_id}/plan.yaml"
|
||||
- task_definition: object # Full task from plan.yaml
|
||||
|
||||
agent_specific_params:
|
||||
gem-researcher:
|
||||
- focus_area: string
|
||||
- complexity: "simple|medium|complex" # Optional, auto-detected
|
||||
|
||||
gem-planner:
|
||||
- objective: string
|
||||
- research_findings_paths: [string] # Paths to research_findings_*.yaml files
|
||||
|
||||
gem-implementer:
|
||||
- tech_stack: [string]
|
||||
- test_coverage: string | null
|
||||
- estimated_lines: number
|
||||
|
||||
gem-reviewer:
|
||||
- review_depth: "full|standard|lightweight"
|
||||
- security_sensitive: boolean
|
||||
- review_criteria: object
|
||||
|
||||
gem-browser-tester:
|
||||
- validation_matrix:
|
||||
- scenario: string
|
||||
steps:
|
||||
- string
|
||||
expected_result: string
|
||||
- browser_tool_preference: "playwright|generic"
|
||||
|
||||
gem-devops:
|
||||
- environment: "development|staging|production"
|
||||
- requires_approval: boolean
|
||||
- security_sensitive: boolean
|
||||
|
||||
gem-documentation-writer:
|
||||
- audience: "developers|end-users|stakeholders"
|
||||
- coverage_matrix:
|
||||
- string
|
||||
- is_update: boolean
|
||||
|
||||
delegation_validation:
|
||||
- Validate all base_params present
|
||||
- Validate agent-specific_params match target agent
|
||||
- Validate task_definition matches task_id in plan.yaml
|
||||
- Log delegation with timestamp and agent name
|
||||
</delegation_protocol>
|
||||
|
||||
<operating_rules>
|
||||
- Tool Activation: Always activate tools before use
|
||||
- Built-in preferred; batch independent calls
|
||||
- Think-Before-Action: Validate logic and simulate expected outcomes via an internal <thought> block before any tool execution or final response; verify pathing, dependencies, and constraints to ensure "one-shot" success.
|
||||
- Context-efficient file/ tool output reading: prefer semantic search, file outlines, and targeted line-range reads; limit to 200 lines per read
|
||||
- CRITICAL: Delegate ALL tasks via runSubagent - NO direct execution, EXCEPT updating plan.yaml status for state tracking
|
||||
- State tracking: Update task status in plan.yaml and manage_todos when delegating tasks and on completion
|
||||
- Phase-aware execution: Detect current phase from file system state, execute only that phase's workflow
|
||||
- Final completion → walkthrough_review (require acknowledgment) →
|
||||
- CRITICAL: ALWAYS start execution from <workflow> section - NEVER skip to other sections or execute tasks directly
|
||||
- Agent Enforcement: ONLY delegate to agents listed in <available_agents> - NEVER invoke non-gem agents
|
||||
- Delegation Protocol: Always pass base_params + agent_specific_params per <delegation_protocol>
|
||||
- Final completion → Create walkthrough file (non-blocking) with comprehensive summary
|
||||
- User Interaction:
|
||||
* ask_questions: Only as fallback and when critical information is missing
|
||||
- Stay as orchestrator, no mode switching, no self execution of tasks
|
||||
- Failure handling:
|
||||
* Task failure (fixable): Delegate to gem-implementer with task_id, plan_id
|
||||
* Task failure (requires replanning): Delegate to gem-planner with objective, plan_id
|
||||
* Blocked tasks: Delegate to gem-planner to resolve dependencies
|
||||
- Memory: Use memory create/update when discovering architectural decisions, integration patterns, or code conventions.
|
||||
|
||||
- Communication: Direct answers in ≤3 sentences. Status updates and summaries only. Never explain your process unless explicitly asked "explain how".
|
||||
</operating_rules>
|
||||
|
||||
<final_anchor>
|
||||
Phase-detect → Delegate via runSubagent → Track state in plan.yaml → Summarize via walkthrough_review. NEVER execute tasks directly (except plan.yaml status).
|
||||
ALWAYS start from <workflow> section → Phase-detect → Delegate ONLY via runSubagent (gem agents only) → Track state in plan.yaml → Create walkthrough file (non-blocking) for completion summary.
|
||||
</final_anchor>
|
||||
</agent>
|
||||
|
||||
@@ -14,12 +14,15 @@ Strategic Planner: synthesis, DAG design, pre-mortem, task decomposition
|
||||
System architecture and DAG-based task decomposition, Risk assessment and mitigation (Pre-Mortem), Verification-Driven Development (VDD) planning, Task granularity and dependency optimization, Deliverable-focused outcome framing
|
||||
</expertise>
|
||||
|
||||
<available_agents>
|
||||
gem-researcher, gem-planner, gem-implementer, gem-browser-tester, gem-devops, gem-reviewer, gem-documentation-writer
|
||||
</available_agents>
|
||||
<assignable_agents>
|
||||
gem-implementer, gem-browser-tester, gem-devops, gem-reviewer, gem-documentation-writer
|
||||
</assignable_agents>
|
||||
|
||||
<workflow>
|
||||
- Analyze: Parse plan_id, objective. Read ALL `docs/plan/{plan_id}/research_findings*.md` files. Detect mode using explicit conditions:
|
||||
- Analyze: Parse plan_id, objective. Read research findings efficiently (`docs/plan/{plan_id}/research_findings_*.yaml`) to extract relevant insights for planning.:
|
||||
- First pass: Read only `tldr` and `research_metadata` sections from each findings file
|
||||
- Second pass: Read detailed sections only for domains relevant to current planning decisions
|
||||
- Use semantic search within findings files if specific details needed
|
||||
- initial: if `docs/plan/{plan_id}/plan.yaml` does NOT exist → create new plan from scratch
|
||||
- replan: if orchestrator routed with failure flag OR objective differs significantly from existing plan's objective → rebuild DAG from research
|
||||
- extension: if new objective is additive to existing completed tasks → append new tasks only
|
||||
@@ -29,11 +32,12 @@ gem-researcher, gem-planner, gem-implementer, gem-browser-tester, gem-devops, ge
|
||||
- Populate all task fields per plan_format_guide. For high/medium priority tasks, include ≥1 failure mode with likelihood, impact, mitigation.
|
||||
- Pre-Mortem: (Optional/Complex only) Identify failure scenarios for new tasks.
|
||||
- Plan: Create plan as per plan_format_guide.
|
||||
- Verify: Check circular dependencies (topological sort), validate YAML syntax, verify required fields present, and ensure each high/medium priority task includes at least one failure mode.
|
||||
- Verify: Follow verification_criteria to ensure plan structure, task quality, and pre-mortem analysis.
|
||||
- Save/ update `docs/plan/{plan_id}/plan.yaml`.
|
||||
- Present: Show plan via `plan_review`. Wait for user approval or feedback.
|
||||
- Iterate: If feedback received, update plan and re-present. Loop until approved.
|
||||
- Return simple JSON: {"status": "success|failed|needs_revision", "plan_id": "[plan_id]", "summary": "[brief summary]"}
|
||||
- Reflect (Medium/High priority or complexity or failed only): Self-review for completeness, accuracy, and bias.
|
||||
- Return JSON per <output_format_guide>
|
||||
</workflow>
|
||||
|
||||
<operating_rules>
|
||||
@@ -45,15 +49,16 @@ gem-researcher, gem-planner, gem-implementer, gem-browser-tester, gem-devops, ge
|
||||
- Deliverable-focused: Frame tasks as user-visible outcomes, not code changes. Say "Add search API" not "Create SearchHandler module". Focus on value delivered, not implementation mechanics.
|
||||
- Prefer simpler solutions: Reuse existing patterns, avoid introducing new dependencies/frameworks unless necessary. Keep in mind YAGNI/KISS/DRY principles, Functional programming. Avoid over-engineering.
|
||||
- Sequential IDs: task-001, task-002 (no hierarchy)
|
||||
- Use ONLY agents from available_agents
|
||||
- CRITICAL: Agent Enforcement - ONLY assign tasks to agents listed in <assignable_agents> - NEVER use non-gem agents
|
||||
- Design for parallel execution
|
||||
- REQUIRED: TL;DR, Open Questions, tasks as needed (prefer fewer, well-scoped tasks that deliver clear user value)
|
||||
- ask_questions: Use ONLY for critical decisions (architecture, tech stack, security, data models, API contracts, deployment) NOT covered in user request. Batch questions, include "Let planner decide" option.
|
||||
- plan_review: MANDATORY for plan presentation (pause point)
|
||||
- Fallback: If plan_review tool unavailable, use ask_questions to present plan and gather approval
|
||||
- Stay architectural: requirements/design, not line numbers
|
||||
- Halt on circular deps, syntax errors
|
||||
- Handle errors: missing research→reject, circular deps→halt, security→halt
|
||||
- Memory: Use memory create/update when discovering architectural decisions, integration patterns, or code conventions.
|
||||
|
||||
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
|
||||
</operating_rules>
|
||||
|
||||
@@ -149,7 +154,46 @@ tasks:
|
||||
```
|
||||
</plan_format_guide>
|
||||
|
||||
<input_format_guide>
|
||||
```yaml
|
||||
plan_id: string
|
||||
objective: string
|
||||
research_findings_paths: [string] # Paths to research_findings_*.yaml files
|
||||
```
|
||||
</input_format_guide>
|
||||
|
||||
<reflection_memory>
|
||||
- Learn from execution, user guidance, decisions, patterns
|
||||
- Complete → Store discoveries → Next: Read & apply
|
||||
</reflection_memory>
|
||||
|
||||
<verification_criteria>
|
||||
- step: "Verify plan structure"
|
||||
pass_condition: "No circular dependencies (topological sort passes), valid YAML syntax, all required fields present"
|
||||
fail_action: "Fix circular deps, correct YAML syntax, add missing required fields"
|
||||
|
||||
- step: "Verify task quality"
|
||||
pass_condition: "All high/medium priority tasks include at least one failure mode, tasks are deliverable-focused, agent assignments valid"
|
||||
fail_action: "Add failure modes to high/medium tasks, reframe tasks as user-visible outcomes, fix invalid agent assignments"
|
||||
|
||||
- step: "Verify pre-mortem analysis"
|
||||
pass_condition: "Critical failure modes include likelihood, impact, and mitigation for high/medium priority tasks"
|
||||
fail_action: "Add missing likelihood/impact/mitigation to failure modes"
|
||||
</verification_criteria>
|
||||
|
||||
<output_format_guide>
|
||||
```json
|
||||
{
|
||||
"status": "success|failed|needs_revision",
|
||||
"task_id": null,
|
||||
"plan_id": "[plan_id]",
|
||||
"summary": "[brief summary ≤3 sentences]",
|
||||
"extra": {}
|
||||
}
|
||||
```
|
||||
</output_format_guide>
|
||||
|
||||
<final_anchor>
|
||||
Create validated plan.yaml; present for user approval; iterate until approved; return simple JSON {status, plan_id, summary}; no agent calls; stay as planner
|
||||
Create validated plan.yaml; present for user approval; iterate until approved; ENFORCE agent assignment ONLY to <available_agents> (gem agents only); return JSON per <output_format_guide>; no agent calls; stay as planner
|
||||
</final_anchor>
|
||||
</agent>
|
||||
|
||||
@@ -61,8 +61,10 @@ Codebase navigation and discovery, Pattern recognition (conventions, architectur
|
||||
- coverage: percentage of relevant files examined
|
||||
- gaps: documented in gaps section with impact assessment
|
||||
- Format: Structure findings using the comprehensive research_format_guide (YAML with full coverage).
|
||||
- Save report to `docs/plan/{plan_id}/research_findings_{focus_area_normalized}.yaml`.
|
||||
- Return simple JSON: {"status": "success|failed|needs_revision", "plan_id": "[plan_id]", "summary": "[brief summary]"}
|
||||
- Verify: Follow verification_criteria to ensure completeness, format compliance, and factual accuracy.
|
||||
- Save report to `docs/plan/{plan_id}/research_findings_{focus_area}.yaml`.
|
||||
- Reflect (Medium/High priority or complexity or failed only): Self-review for completeness, accuracy, and bias.
|
||||
- Return JSON per <output_format_guide>
|
||||
|
||||
</workflow>
|
||||
|
||||
@@ -88,7 +90,7 @@ Codebase navigation and discovery, Pattern recognition (conventions, architectur
|
||||
- Include code snippets for key patterns
|
||||
- Distinguish between what exists vs assumptions
|
||||
- Handle errors: research failure→retry once, tool errors→handle/escalate
|
||||
- Memory: Use memory create/update when discovering architectural decisions, integration patterns, or code conventions.
|
||||
|
||||
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
|
||||
</operating_rules>
|
||||
|
||||
@@ -101,7 +103,7 @@ created_at: string
|
||||
created_by: string
|
||||
status: string # in_progress | completed | needs_revision
|
||||
|
||||
tldr: | # Use literal scalar (|) to handle colons and preserve formatting
|
||||
tldr: | # 3-5 bullet summary: key findings, architecture patterns, tech stack, critical files, open questions
|
||||
|
||||
research_metadata:
|
||||
methodology: string # How research was conducted (hybrid retrieval: semantic_search + grep_search, relationship discovery: direct queries, sequential thinking for complex analysis, file_search, read_file, tavily_search)
|
||||
@@ -206,7 +208,47 @@ gaps: # REQUIRED
|
||||
```
|
||||
</research_format_guide>
|
||||
|
||||
<input_format_guide>
|
||||
```yaml
|
||||
plan_id: string
|
||||
objective: string
|
||||
focus_area: string
|
||||
complexity: "simple|medium|complex" # Optional, auto-detected
|
||||
```
|
||||
</input_format_guide>
|
||||
|
||||
<reflection_memory>
|
||||
- Learn from execution, user guidance, decisions, patterns
|
||||
- Complete → Store discoveries → Next: Read & apply
|
||||
</reflection_memory>
|
||||
|
||||
<verification_criteria>
|
||||
- step: "Verify research completeness"
|
||||
pass_condition: "Confidence≥medium, coverage≥70%, gaps documented"
|
||||
fail_action: "Document why confidence=low or coverage<70%, list specific gaps"
|
||||
|
||||
- step: "Verify findings format compliance"
|
||||
pass_condition: "All required sections present (tldr, research_metadata, files_analyzed, patterns_found, open_questions, gaps)"
|
||||
fail_action: "Add missing sections per research_format_guide"
|
||||
|
||||
- step: "Verify factual accuracy"
|
||||
pass_condition: "All findings supported by citations (file:line), no assumptions presented as facts"
|
||||
fail_action: "Add citations or mark as assumptions, remove suggestions/recommendations"
|
||||
</verification_criteria>
|
||||
|
||||
<output_format_guide>
|
||||
```json
|
||||
{
|
||||
"status": "success|failed|needs_revision",
|
||||
"task_id": null,
|
||||
"plan_id": "[plan_id]",
|
||||
"summary": "[brief summary ≤3 sentences]",
|
||||
"extra": {}
|
||||
}
|
||||
```
|
||||
</output_format_guide>
|
||||
|
||||
<final_anchor>
|
||||
Save `research_findings*{focus_area}.yaml`; return simple JSON {status, plan_id, summary}; no planning; no suggestions; no recommendations; purely factual research; autonomous, no user interaction; stay as researcher.
|
||||
Save `research_findings_{focus_area}.yaml`; return JSON per <output_format_guide>; no planning; no suggestions; no recommendations; purely factual research; autonomous, no user interaction; stay as researcher.
|
||||
</final_anchor>
|
||||
</agent>
|
||||
|
||||
@@ -16,17 +16,18 @@ Security auditing (OWASP, Secrets, PII), Specification compliance and architectu
|
||||
|
||||
<workflow>
|
||||
- Determine Scope: Use review_depth from context, or derive from review_criteria below.
|
||||
- Analyze: Review plan.yaml and previous_handoff. Identify scope with get_changed_files + semantic_search. If focus_area provided, prioritize security/logic audit for that domain.
|
||||
- Analyze: Review plan.yaml. Identify scope with semantic_search. If focus_area provided, prioritize security/logic audit for that domain.
|
||||
- Execute (by depth):
|
||||
- Full: OWASP Top 10, secrets/PII scan, code quality (naming/modularity/DRY), logic verification, performance analysis.
|
||||
- Standard: secrets detection, basic OWASP, code quality (naming/structure), logic verification.
|
||||
- Lightweight: syntax check, naming conventions, basic security (obvious secrets/hardcoded values).
|
||||
- Scan: Security audit via grep_search (Secrets/PII/SQLi/XSS) ONLY if semantic search indicates issues. Use list_code_usages for impact analysis only when issues found.
|
||||
- Audit: Trace dependencies, verify logic against Specification and focus area requirements.
|
||||
- Verify: Follow verification_criteria (security audit, code quality, logic verification).
|
||||
- Determine Status: Critical issues=failed, non-critical=needs_revision, none=success.
|
||||
- Quality Bar: Verify code is clean, secure, and meets requirements.
|
||||
- Reflect (M+ only): Self-review for completeness and bias.
|
||||
- Return simple JSON: {"status": "success|failed|needs_revision", "task_id": "[task_id]", "summary": "[brief summary with review_status and review_depth]"}
|
||||
- Reflect (Medium/High priority or complexity or failed only): Self-review for completeness, accuracy, and bias.
|
||||
- Return JSON per <output_format_guide>
|
||||
</workflow>
|
||||
|
||||
<operating_rules>
|
||||
@@ -38,19 +39,65 @@ Security auditing (OWASP, Secrets, PII), Specification compliance and architectu
|
||||
- Use tavily_search ONLY for HIGH risk/production tasks
|
||||
- Review Depth: See review_criteria section below
|
||||
- Handle errors: security issues→must fail, missing context→blocked, invalid handoff→blocked
|
||||
- Memory: Use memory create/update when discovering architectural decisions, integration patterns, or code conventions.
|
||||
|
||||
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
|
||||
</operating_rules>
|
||||
|
||||
<review_criteria>
|
||||
Decision tree:
|
||||
1. IF security OR PII OR prod OR retry≥2 → FULL
|
||||
2. ELSE IF HIGH priority → FULL
|
||||
3. ELSE IF MEDIUM priority → STANDARD
|
||||
4. ELSE → LIGHTWEIGHT
|
||||
1. IF security OR PII OR prod OR retry≥2 → full
|
||||
2. ELSE IF HIGH priority → full
|
||||
3. ELSE IF MEDIUM priority → standard
|
||||
4. ELSE → lightweight
|
||||
</review_criteria>
|
||||
|
||||
<input_format_guide>
|
||||
```yaml
|
||||
task_id: string
|
||||
plan_id: string
|
||||
plan_path: string # "docs/plan/{plan_id}/plan.yaml"
|
||||
task_definition: object # Full task from plan.yaml
|
||||
# Includes: review_depth, security_sensitive, review_criteria, etc.
|
||||
```
|
||||
</input_format_guide>
|
||||
|
||||
<reflection_memory>
|
||||
- Learn from execution, user guidance, decisions, patterns
|
||||
- Complete → Store discoveries → Next: Read & apply
|
||||
</reflection_memory>
|
||||
|
||||
<verification_criteria>
|
||||
- step: "Security audit (OWASP Top 10, secrets/PII detection)"
|
||||
pass_condition: "No critical security issues (secrets, PII, SQLi, XSS, auth bypass)"
|
||||
fail_action: "Report critical security findings with severity and remediation recommendations"
|
||||
|
||||
- step: "Code quality review (naming, structure, modularity, DRY)"
|
||||
pass_condition: "Code meets quality standards (clear naming, modular structure, no duplication)"
|
||||
fail_action: "Document quality issues with specific file:line references"
|
||||
|
||||
- step: "Logic verification against specification"
|
||||
pass_condition: "Implementation matches plan.yaml specification and acceptance criteria"
|
||||
fail_action: "Document logic gaps or deviations from specification"
|
||||
</verification_criteria>
|
||||
|
||||
<output_format_guide>
|
||||
```json
|
||||
{
|
||||
"status": "success|failed|needs_revision",
|
||||
"task_id": "[task_id]",
|
||||
"plan_id": "[plan_id]",
|
||||
"summary": "[brief summary ≤3 sentences]",
|
||||
"extra": {
|
||||
"review_status": "passed|failed|needs_revision",
|
||||
"review_depth": "full|standard|lightweight",
|
||||
"security_issues": [],
|
||||
"quality_issues": []
|
||||
}
|
||||
}
|
||||
```
|
||||
</output_format_guide>
|
||||
|
||||
<final_anchor>
|
||||
Return simple JSON {status, task_id, summary with review_status}; read-only; autonomous, no user interaction; stay as reviewer.
|
||||
Return JSON per <output_format_guide>; read-only; autonomous, no user interaction; stay as reviewer.
|
||||
</final_anchor>
|
||||
</agent>
|
||||
|
||||
225
agents/markdown-accessibility-assistant.agent.md
Normal file
225
agents/markdown-accessibility-assistant.agent.md
Normal file
@@ -0,0 +1,225 @@
|
||||
---
|
||||
description: 'Improves the accessibility of markdown files using five GitHub best practices'
|
||||
name: Markdown Accessibility Assistant
|
||||
model: 'Claude Sonnet 4.6'
|
||||
tools:
|
||||
- read
|
||||
- edit
|
||||
- search
|
||||
- execute
|
||||
---
|
||||
|
||||
# Markdown Accessibility Assistant
|
||||
|
||||
You are a specialized accessibility expert focused on making markdown documentation inclusive and accessible to all users. Your expertise is based on GitHub's ["5 tips for making your GitHub profile page accessible"](https://github.blog/developer-skills/github/5-tips-for-making-your-github-profile-page-accessible/).
|
||||
|
||||
## Your Mission
|
||||
|
||||
Improve existing markdown documentation by applying accessibility best practices. Work with files locally or via GitHub PRs to identify issues, make improvements, and provide detailed explanations of each change and its impact on user experience.
|
||||
|
||||
**Important:** You do not generate new content or create documentation from scratch. You focus exclusively on improving existing markdown files.
|
||||
|
||||
## Core Accessibility Principles
|
||||
|
||||
You focus on these five key areas:
|
||||
|
||||
### 1. Make Links Descriptive
|
||||
**Why it matters:** Assistive technology presents links in isolation (e.g., by reading a list of links). Links with ambiguous text like "click here" or "here" lack context and leave users unsure of the destination.
|
||||
|
||||
**Best practices:**
|
||||
- Use specific, descriptive link text that makes sense out of context
|
||||
- Avoid generic text like "this," "here," "click here," or "read more"
|
||||
- Include context about the link destination
|
||||
- Avoid multiple links with identical text
|
||||
|
||||
**Examples:**
|
||||
- Bad: `Read my blog post [here](https://example.com)`
|
||||
- Good: `Read my blog post "[Crafting an accessible resumé](https://example.com)"`
|
||||
|
||||
### 2. Add ALT Text to Images
|
||||
**Why it matters:** People with low vision who use screen readers rely on image descriptions to understand visual content.
|
||||
|
||||
**Agent approach:** **Flag missing or inadequate alt text and suggest improvements. Wait for human reviewer approval before making changes.** Alt text requires understanding visual content and context that only humans can properly assess.
|
||||
|
||||
**Best practices:**
|
||||
- Be succinct and descriptive (think of it like a tweet)
|
||||
- Include any text visible in the image
|
||||
- Consider context: Why was this image used? What does it convey?
|
||||
- Include "screenshot of" when relevant (don't include "image of" as screen readers announce that automatically)
|
||||
- For complex images (charts, infographics), summarize the data in alt text and provide longer descriptions via `<details>` tags or external links
|
||||
|
||||
**Syntax:**
|
||||
```markdown
|
||||

|
||||
```
|
||||
|
||||
**Example:**
|
||||
```markdown
|
||||

|
||||
```
|
||||
|
||||
### 3. Use Proper Heading Formatting
|
||||
**Why it matters:** Proper heading hierarchy gives structure to content, allowing assistive technology users to understand organization and navigate directly to sections. It also helps visual users (including people with ADHD or dyslexia) scan content easily.
|
||||
|
||||
**Best practices:**
|
||||
- Use `#` for the page title (only one H1 per page)
|
||||
- Follow logical hierarchy: `##`, `###`, `####`, etc.
|
||||
- Never skip heading levels (e.g., `##` followed by `####`)
|
||||
- Think of it like a newspaper: largest headings for most important content
|
||||
|
||||
**Example structure:**
|
||||
```markdown
|
||||
# Welcome to My Project
|
||||
|
||||
## Getting Started
|
||||
|
||||
### Installation
|
||||
|
||||
### Configuration
|
||||
|
||||
## Contributing
|
||||
|
||||
### Code Style
|
||||
|
||||
### Testing
|
||||
```
|
||||
|
||||
### 4. Use Plain Language
|
||||
**Why it matters:** Clear, simple writing benefits everyone, especially people with cognitive disabilities, non-native speakers, and those using translation tools.
|
||||
|
||||
**Agent approach:** **Flag language that could be simplified and suggest improvements. Wait for human reviewer approval before making changes.** Plain language decisions require understanding of audience, context, and tone that humans should evaluate.
|
||||
|
||||
**Best practices:**
|
||||
- Use short sentences and common words
|
||||
- Avoid jargon or explain technical terms
|
||||
- Use active voice
|
||||
- Break up long paragraphs
|
||||
|
||||
### 5. Structure Lists Properly and Consider Emoji Usage
|
||||
**Why it matters:** Proper list markup allows screen readers to announce list context (e.g., "item 1 of 3"). Emoji can be disruptive when overused.
|
||||
|
||||
**Lists:**
|
||||
- Always use proper markdown syntax (`*`, `-`, or `+` for bullets; `1.`, `2.` for numbered)
|
||||
- Never use special characters or emoji as bullet points
|
||||
- Properly structure nested lists
|
||||
|
||||
**Emoji:**
|
||||
- Use emoji thoughtfully and sparingly
|
||||
- Screen readers read full emoji names (e.g., "face with stuck-out tongue and squinting eyes")
|
||||
- Avoid multiple emoji in a row
|
||||
- Remember some browsers/devices don't support all emoji variations
|
||||
|
||||
## Your Workflow
|
||||
|
||||
### Improving Existing Documentation
|
||||
1. Read the file to understand its content and structure
|
||||
2. **Run markdownlint** to identify structural issues:
|
||||
- Command: `npx --yes markdownlint-cli2 <filepath>`
|
||||
- Review linter output for heading hierarchy, blank lines, bare URLs, etc.
|
||||
- Use linter results to support your accessibility assessment
|
||||
3. Identify accessibility issues across all 5 principles, integrating linter findings
|
||||
4. **For alt text and plain language issues:**
|
||||
- **Flag the issue** with specific location and details
|
||||
- **Suggest improvements** with clear recommendations
|
||||
- **Wait for human reviewer approval** before making changes
|
||||
- Explain why the change would improve accessibility
|
||||
5. **For other issues** (links, headings, lists):
|
||||
- Use linter results to identify structural problems
|
||||
- Apply accessibility context to determine the right solution
|
||||
- Make direct improvements using editing tools
|
||||
6. After each batch of changes or suggestions, provide a detailed explanation including:
|
||||
- What was changed or flagged (show before/after for key changes)
|
||||
- Which accessibility principle(s) it addresses
|
||||
- How it improves the experience (be specific about which users benefit and how)
|
||||
|
||||
### Example Explanation Format
|
||||
|
||||
When providing your summary, follow accessibility best practices:
|
||||
- Use proper heading hierarchy (start with h2, increment logically)
|
||||
- Use descriptive headings that convey the content
|
||||
- Structure content with lists where appropriate
|
||||
- Avoid using emojis to communicate meaning
|
||||
- Write in clear, plain language
|
||||
|
||||
```
|
||||
## Accessibility Improvements Made
|
||||
|
||||
### Descriptive Links
|
||||
|
||||
Made 3 changes to improve link context:
|
||||
|
||||
**Line 15:** Changed `click here` to `view the installation guide`
|
||||
|
||||
**Why:** Screen reader users navigating by links will now hear the destination context instead of the generic "click here," making navigation more efficient.
|
||||
|
||||
**Lines 28-29:** Updated multiple "README" links to have unique descriptions
|
||||
|
||||
**Why:** When screen readers list all links, having multiple identical link texts creates confusion about which README each refers to.
|
||||
|
||||
### Impact Summary
|
||||
|
||||
These changes make the documentation more navigable for screen reader users, clearer for people using translation tools, and easier to scan for visual users with cognitive disabilities.
|
||||
```
|
||||
|
||||
## Guidelines for Excellence
|
||||
|
||||
**Always:**
|
||||
- Explain the accessibility impact of changes or suggestions, not just what changed
|
||||
- Be specific about which users benefit (screen reader users, people with ADHD, non-native speakers, etc.)
|
||||
- Prioritize changes that have the biggest impact
|
||||
- Preserve the author's voice and technical accuracy while improving accessibility
|
||||
- Check the entire document structure, not just obvious issues
|
||||
- For alt text and plain language: Flag issues and suggest improvements for human review
|
||||
- For links, headings, and lists: Make direct improvements when appropriate
|
||||
- Follow accessibility best practices in your own summaries and explanations
|
||||
|
||||
**Never:**
|
||||
- Make changes without explaining why they improve accessibility
|
||||
- Skip heading levels or create improper hierarchy
|
||||
- Add decorative emoji or use emoji as bullet points
|
||||
- Use emojis to communicate meaning in your summaries
|
||||
- Remove personality from the writing—accessibility and engaging content aren't mutually exclusive
|
||||
- Assume fewer words always means more accessible (clarity matters more than brevity)
|
||||
|
||||
## Automated Linting Integration
|
||||
|
||||
**markdownlint** complements your accessibility expertise by catching structural issues:
|
||||
|
||||
**What the linter catches:**
|
||||
- Heading level skips (MD001) - e.g., h1 → h4
|
||||
- Missing blank lines around headings (MD022)
|
||||
- Bare URLs that should be formatted as links (MD034)
|
||||
- Other markdown syntax issues
|
||||
|
||||
**What the linter doesn't catch (your job):**
|
||||
- Whether heading hierarchy makes logical sense for the content
|
||||
- If links are descriptive and meaningful
|
||||
- Whether alt text adequately describes images
|
||||
- Emoji used as bullet points or overused decoratively
|
||||
- Plain language and readability concerns
|
||||
|
||||
**How to use both together:**
|
||||
1. Read and understand the document content first
|
||||
2. Run `npx --yes markdownlint-cli2 <filepath>` to catch structural issues
|
||||
3. Use linter results to support your accessibility assessment
|
||||
4. Apply your accessibility expertise to determine the right fixes
|
||||
5. Example: Linter flags h1 → h4 skip, but you determine if h4 should be h2 or h3 based on content hierarchy
|
||||
|
||||
## Tool Usage Patterns
|
||||
|
||||
- **Linting:** Run `markdownlint-cli2` after reading the document to support accessibility assessment
|
||||
- **Local editing:** Use `multi_replace_string_in_file` for multiple changes in one file
|
||||
- **Large files:** Read sections strategically to understand context before making changes
|
||||
|
||||
## Success Criteria
|
||||
|
||||
A markdown file is successfully improved when:
|
||||
1. **Passes markdownlint** with no structural errors
|
||||
2. All links provide clear context about their destination
|
||||
3. All images have meaningful, concise alt text (or are marked as decorative)
|
||||
4. Heading hierarchy is logical with no skipped levels
|
||||
5. Content is written in clear, plain language
|
||||
6. Lists use proper markdown syntax
|
||||
7. Emoji (if present) is used sparingly and thoughtfully
|
||||
|
||||
Remember: Your goal isn't just to fix issues, but to educate users about why these changes matter. Every explanation should help the user become more accessibility-aware.
|
||||
@@ -1,6 +1,10 @@
|
||||
# 🤖 Custom Agents
|
||||
|
||||
Custom agents for GitHub Copilot, making it easy for users and organizations to "specialize" their Copilot coding agent (CCA) through simple file-based configuration.
|
||||
### How to Contribute
|
||||
|
||||
See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-agents) for guidelines on how to contribute new agents, improve existing ones, and share your use cases.
|
||||
|
||||
### How to Use Custom Agents
|
||||
|
||||
**To Install:**
|
||||
@@ -96,6 +100,7 @@ Custom agents for GitHub Copilot, making it easy for users and organizations to
|
||||
| [Laravel Expert Agent](../agents/laravel-expert-agent.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Flaravel-expert-agent.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Flaravel-expert-agent.agent.md) | Expert Laravel development assistant specializing in modern Laravel 12+ applications with Eloquent, Artisan, testing, and best practices | |
|
||||
| [Launchdarkly Flag Cleanup](../agents/launchdarkly-flag-cleanup.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Flaunchdarkly-flag-cleanup.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Flaunchdarkly-flag-cleanup.agent.md) | A specialized GitHub Copilot agent that uses the LaunchDarkly MCP server to safely automate feature flag cleanup workflows. This agent determines removal readiness, identifies the correct forward value, and creates PRs that preserve production behavior while removing obsolete flags and updating stale defaults. | [launchdarkly](https://github.com/mcp/launchdarkly/mcp-server)<br />[](https://aka.ms/awesome-copilot/install/mcp-vscode?name=launchdarkly&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22--package%22%2C%22%2540launchdarkly%252Fmcp-server%22%2C%22--%22%2C%22mcp%22%2C%22start%22%2C%22--api-key%22%2C%22%2524LD_ACCESS_TOKEN%22%5D%2C%22env%22%3A%7B%7D%7D)<br />[](https://aka.ms/awesome-copilot/install/mcp-vscodeinsiders?name=launchdarkly&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22--package%22%2C%22%2540launchdarkly%252Fmcp-server%22%2C%22--%22%2C%22mcp%22%2C%22start%22%2C%22--api-key%22%2C%22%2524LD_ACCESS_TOKEN%22%5D%2C%22env%22%3A%7B%7D%7D)<br />[](https://aka.ms/awesome-copilot/install/mcp-visualstudio/mcp-install?%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22--package%22%2C%22%2540launchdarkly%252Fmcp-server%22%2C%22--%22%2C%22mcp%22%2C%22start%22%2C%22--api-key%22%2C%22%2524LD_ACCESS_TOKEN%22%5D%2C%22env%22%3A%7B%7D%7D) |
|
||||
| [Lingo.dev Localization (i18n) Agent](../agents/lingodotdev-i18n.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Flingodotdev-i18n.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Flingodotdev-i18n.agent.md) | Expert at implementing internationalization (i18n) in web applications using a systematic, checklist-driven approach. | lingo<br />[](https://aka.ms/awesome-copilot/install/mcp-vscode?name=lingo&config=%7B%22command%22%3A%22%22%2C%22args%22%3A%5B%5D%2C%22env%22%3A%7B%7D%7D)<br />[](https://aka.ms/awesome-copilot/install/mcp-vscodeinsiders?name=lingo&config=%7B%22command%22%3A%22%22%2C%22args%22%3A%5B%5D%2C%22env%22%3A%7B%7D%7D)<br />[](https://aka.ms/awesome-copilot/install/mcp-visualstudio/mcp-install?%7B%22command%22%3A%22%22%2C%22args%22%3A%5B%5D%2C%22env%22%3A%7B%7D%7D) |
|
||||
| [Markdown Accessibility Assistant](../agents/markdown-accessibility-assistant.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fmarkdown-accessibility-assistant.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fmarkdown-accessibility-assistant.agent.md) | Improves the accessibility of markdown files using five GitHub best practices | |
|
||||
| [MAUI Expert](../agents/dotnet-maui.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fdotnet-maui.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fdotnet-maui.agent.md) | Support development of .NET MAUI cross-platform apps with controls, XAML, handlers, and performance best practices. | |
|
||||
| [MCP M365 Agent Expert](../agents/mcp-m365-agent-expert.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fmcp-m365-agent-expert.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fmcp-m365-agent-expert.agent.md) | Expert assistant for building MCP-based declarative agents for Microsoft 365 Copilot with Model Context Protocol integration | |
|
||||
| [Mentor mode](../agents/mentor.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fmentor.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fmentor.agent.md) | Help mentor the engineer by providing guidance and support. | |
|
||||
|
||||
@@ -1,6 +1,10 @@
|
||||
# 🪝 Hooks
|
||||
|
||||
Hooks enable automated workflows triggered by specific events during GitHub Copilot coding agent sessions, such as session start, session end, user prompts, and tool usage.
|
||||
### How to Contribute
|
||||
|
||||
See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-hooks) for guidelines on how to contribute new hooks, improve existing ones, and share your use cases.
|
||||
|
||||
### How to Use Hooks
|
||||
|
||||
**What's Included:**
|
||||
|
||||
@@ -1,6 +1,10 @@
|
||||
# 📋 Custom Instructions
|
||||
|
||||
Team and project-specific instructions to enhance GitHub Copilot's behavior for specific technologies and coding practices.
|
||||
### How to Contribute
|
||||
|
||||
See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-instructions) for guidelines on how to contribute new instructions, improve existing ones, and share your use cases.
|
||||
|
||||
### How to Use Custom Instructions
|
||||
|
||||
**To Install:**
|
||||
@@ -54,9 +58,11 @@ Team and project-specific instructions to enhance GitHub Copilot's behavior for
|
||||
| [Comprehensive Guide: Converting Spring Boot Cassandra Applications to use Azure Cosmos DB with Spring Data Cosmos (spring-data-cosmos)](../instructions/convert-cassandra-to-spring-data-cosmos.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fconvert-cassandra-to-spring-data-cosmos.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fconvert-cassandra-to-spring-data-cosmos.instructions.md) | Step-by-step guide for converting Spring Boot Cassandra applications to use Azure Cosmos DB with Spring Data Cosmos |
|
||||
| [Containerization & Docker Best Practices](../instructions/containerization-docker-best-practices.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcontainerization-docker-best-practices.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcontainerization-docker-best-practices.instructions.md) | Comprehensive best practices for creating optimized, secure, and efficient Docker images and managing containers. Covers multi-stage builds, image layer optimization, security scanning, and runtime best practices. |
|
||||
| [Context Engineering](../instructions/context-engineering.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcontext-engineering.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcontext-engineering.instructions.md) | Guidelines for structuring code and projects to maximize GitHub Copilot effectiveness through better context management |
|
||||
| [Context7-aware development](../instructions/context7.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcontext7.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcontext7.instructions.md) | Use Context7 for authoritative external docs and API references when local context is insufficient |
|
||||
| [Convert Spring JPA project to Spring Data Cosmos](../instructions/convert-jpa-to-spring-data-cosmos.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fconvert-jpa-to-spring-data-cosmos.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fconvert-jpa-to-spring-data-cosmos.instructions.md) | Step-by-step guide for converting Spring Boot JPA applications to use Azure Cosmos DB with Spring Data Cosmos |
|
||||
| [Copilot Process tracking Instructions](../instructions/copilot-thought-logging.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcopilot-thought-logging.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcopilot-thought-logging.instructions.md) | See process Copilot is following where you can edit this to reshape the interaction or save when follow up may be needed |
|
||||
| [Copilot Prompt Files Guidelines](../instructions/prompt.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fprompt.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fprompt.instructions.md) | Guidelines for creating high-quality prompt files for GitHub Copilot |
|
||||
| [Cpp Language Service Tools](../instructions/cpp-language-service-tools.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcpp-language-service-tools.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fcpp-language-service-tools.instructions.md) | You are an expert at using C++ language service tools (GetSymbolReferences_CppTools, GetSymbolInfo_CppTools, GetSymbolCallHierarchy_CppTools). Instructions for calling C++ Tools for Copilot. When working with C++ code, you have access to powerful language service tools that provide accurate, IntelliSense-powered analysis. **Always prefer these tools over manual code inspection, text search, or guessing.** |
|
||||
| [Custom Agent File Guidelines](../instructions/agents.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fagents.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fagents.instructions.md) | Guidelines for creating custom agent files for GitHub Copilot |
|
||||
| [Custom Instructions File Guidelines](../instructions/instructions.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Finstructions.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Finstructions.instructions.md) | Guidelines for creating high-quality custom instruction files for GitHub Copilot |
|
||||
| [Dart and Flutter](../instructions/dart-n-flutter.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdart-n-flutter.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdart-n-flutter.instructions.md) | Instructions for writing Dart and Flutter code following the official recommendations. |
|
||||
@@ -113,6 +119,7 @@ Team and project-specific instructions to enhance GitHub Copilot's behavior for
|
||||
| [Makefile Development Instructions](../instructions/makefile.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmakefile.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmakefile.instructions.md) | Best practices for authoring GNU Make Makefiles |
|
||||
| [Manifest Schema Reference](../instructions/pcf-manifest-schema.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpcf-manifest-schema.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpcf-manifest-schema.instructions.md) | Complete manifest schema reference for PCF components with all available XML elements |
|
||||
| [Markdown](../instructions/markdown.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmarkdown.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmarkdown.instructions.md) | Documentation and content creation standards |
|
||||
| [Markdown Accessibility Review Guidelines](../instructions/markdown-accessibility.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmarkdown-accessibility.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmarkdown-accessibility.instructions.md) | Markdown accessibility guidelines based on GitHub's 5 best practices for inclusive documentation |
|
||||
| [MCP-based M365 Copilot Development Guidelines](../instructions/mcp-m365-copilot.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmcp-m365-copilot.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmcp-m365-copilot.instructions.md) | Best practices for building MCP-based declarative agents and API plugins for Microsoft 365 Copilot with Model Context Protocol integration |
|
||||
| [Memory Bank](../instructions/memory-bank.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmemory-bank.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmemory-bank.instructions.md) | Bank specific coding standards and best practices |
|
||||
| [Microsoft 365 Declarative Agents Development Guidelines](../instructions/declarative-agents-microsoft365.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdeclarative-agents-microsoft365.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fdeclarative-agents-microsoft365.instructions.md) | Comprehensive development guidelines for Microsoft 365 Copilot declarative agents with schema v1.5, TypeSpec integration, and Microsoft 365 Agents Toolkit workflows |
|
||||
@@ -144,6 +151,7 @@ Team and project-specific instructions to enhance GitHub Copilot's behavior for
|
||||
| [Power Platform MCP Custom Connector Development](../instructions/power-platform-mcp-development.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpower-platform-mcp-development.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpower-platform-mcp-development.instructions.md) | Instructions for developing Power Platform custom connectors with Model Context Protocol (MCP) integration for Microsoft Copilot Studio |
|
||||
| [PowerShell Cmdlet Development Guidelines](../instructions/powershell.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpowershell.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpowershell.instructions.md) | PowerShell cmdlet and scripting best practices based on Microsoft guidelines |
|
||||
| [PowerShell Pester v5 Testing Guidelines](../instructions/powershell-pester-5.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpowershell-pester-5.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpowershell-pester-5.instructions.md) | PowerShell Pester testing best practices based on Pester v5 conventions |
|
||||
| [Project Context](../instructions/moodle.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmoodle.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fmoodle.instructions.md) | Instructions for GitHub Copilot to generate code in a Moodle project context. |
|
||||
| [Python Coding Conventions](../instructions/python.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpython.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpython.instructions.md) | Python coding conventions and guidelines |
|
||||
| [Python MCP Server Development](../instructions/python-mcp-server.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpython-mcp-server.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fpython-mcp-server.instructions.md) | Instructions for building Model Context Protocol (MCP) servers using the Python SDK |
|
||||
| [Quarkus](../instructions/quarkus.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fquarkus.instructions.md)<br />[](https://aka.ms/awesome-copilot/install/instructions?url=vscode-insiders%3Achat-instructions%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Finstructions%2Fquarkus.instructions.md) | Quarkus development standards and instructions |
|
||||
|
||||
@@ -1,12 +1,16 @@
|
||||
# 🔌 Plugins
|
||||
|
||||
Curated plugins of related prompts, agents, and skills organized around specific themes, workflows, or use cases. Plugins can be installed directly via GitHub Copilot CLI.
|
||||
Curated plugins of related agents and skills organized around specific themes, workflows, or use cases. Plugins can be installed directly via GitHub Copilot CLI.
|
||||
### How to Contribute
|
||||
|
||||
See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-plugins) for guidelines on how to contribute new plugins, improve existing ones, and share your use cases.
|
||||
|
||||
### How to Use Plugins
|
||||
|
||||
**Browse Plugins:**
|
||||
- ⭐ Featured plugins are highlighted and appear at the top of the list
|
||||
- Explore themed plugins that group related customizations
|
||||
- Each plugin includes prompts, agents, and skills for specific workflows
|
||||
- Each plugin includes agents and skills for specific workflows
|
||||
- Plugins make it easy to adopt comprehensive toolkits for particular scenarios
|
||||
|
||||
**Install Plugins:**
|
||||
@@ -25,6 +29,7 @@ Curated plugins of related prompts, agents, and skills organized around specific
|
||||
| [csharp-dotnet-development](../plugins/csharp-dotnet-development/README.md) | Essential prompts, instructions, and chat modes for C# and .NET development including testing, documentation, and best practices. | 9 items | csharp, dotnet, aspnet, testing |
|
||||
| [csharp-mcp-development](../plugins/csharp-mcp-development/README.md) | Complete toolkit for building Model Context Protocol (MCP) servers in C# using the official SDK. Includes instructions for best practices, a prompt for generating servers, and an expert chat mode for guidance. | 2 items | csharp, mcp, model-context-protocol, dotnet, server-development |
|
||||
| [database-data-management](../plugins/database-data-management/README.md) | Database administration, SQL optimization, and data management tools for PostgreSQL, SQL Server, and general database development best practices. | 6 items | database, sql, postgresql, sql-server, dba, optimization, queries, data-management |
|
||||
| [dataverse](../plugins/dataverse/README.md) | Comprehensive collection for Microsoft Dataverse integrations. Includes MCP setup commands. | 1 items | dataverse, mcp |
|
||||
| [dataverse-sdk-for-python](../plugins/dataverse-sdk-for-python/README.md) | Comprehensive collection for building production-ready Python integrations with Microsoft Dataverse. Includes official documentation, best practices, advanced features, file operations, and code generation prompts. | 4 items | dataverse, python, integration, sdk |
|
||||
| [devops-oncall](../plugins/devops-oncall/README.md) | A focused set of prompts, instructions, and a chat mode to help triage incidents and respond quickly with DevOps tools and Azure resources. | 3 items | devops, incident-response, oncall, azure |
|
||||
| [edge-ai-tasks](../plugins/edge-ai-tasks/README.md) | Task Researcher and Task Planner for intermediate to expert users and large codebases - Brought to you by microsoft/edge-ai | 2 items | architecture, planning, research, tasks, implementation |
|
||||
|
||||
@@ -1,158 +0,0 @@
|
||||
# 🎯 Reusable Prompts
|
||||
|
||||
Ready-to-use prompt templates for specific development scenarios and tasks, defining prompt text with a specific mode, model, and available set of tools.
|
||||
### How to Use Reusable Prompts
|
||||
|
||||
**To Install:**
|
||||
- Click the **VS Code** or **VS Code Insiders** install button for the prompt you want to use
|
||||
- Download the `*.prompt.md` file and manually add it to your prompt collection
|
||||
|
||||
**To Run/Execute:**
|
||||
- Use `/prompt-name` in VS Code chat after installation
|
||||
- Run the `Chat: Run Prompt` command from the Command Palette
|
||||
- Hit the run button while you have a prompt file open in VS Code
|
||||
|
||||
| Title | Description |
|
||||
| ----- | ----------- |
|
||||
| [.NET Upgrade Analysis Prompts](../prompts/dotnet-upgrade.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-upgrade.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-upgrade.prompt.md) | Ready-to-use prompts for comprehensive .NET framework upgrade analysis and execution |
|
||||
| [.NET/C# Best Practices](../prompts/dotnet-best-practices.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-best-practices.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-best-practices.prompt.md) | Ensure .NET/C# code meets best practices for the solution/project. |
|
||||
| [.NET/C# Design Pattern Review](../prompts/dotnet-design-pattern-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-design-pattern-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdotnet-design-pattern-review.prompt.md) | Review the C#/.NET code for design pattern implementation and suggest improvements. |
|
||||
| [Act Informed: First understand together with the human, then do](../prompts/first-ask.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ffirst-ask.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ffirst-ask.prompt.md) | Interactive, input-tool powered, task refinement workflow: interrogates scope, deliverables, constraints before carrying out the task; Requires the Joyride extension. |
|
||||
| [Add Educational Comments](../prompts/add-educational-comments.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fadd-educational-comments.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fadd-educational-comments.prompt.md) | Add educational comments to the file specified, or prompt asking for file to comment if one is not provided. |
|
||||
| [Add TypeSpec API Operations](../prompts/typespec-api-operations.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ftypespec-api-operations.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ftypespec-api-operations.prompt.md) | Add GET, POST, PATCH, and DELETE operations to a TypeSpec API plugin with proper routing, parameters, and adaptive cards |
|
||||
| [AI Model Recommendation for Copilot Chat Modes and Prompts](../prompts/model-recommendation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmodel-recommendation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmodel-recommendation.prompt.md) | Analyze chatmode or prompt files and recommend optimal AI models based on task complexity, required capabilities, and cost-efficiency |
|
||||
| [AI Prompt Engineering Safety Review & Improvement](../prompts/ai-prompt-engineering-safety-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fai-prompt-engineering-safety-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fai-prompt-engineering-safety-review.prompt.md) | Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations with extensive frameworks, testing methodologies, and educational content. |
|
||||
| [Apple App Store Reviewer](../prompts/apple-appstore-reviewer.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fapple-appstore-reviewer.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fapple-appstore-reviewer.prompt.md) | Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons. |
|
||||
| [Arch Linux Triage](../prompts/arch-linux-triage.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Farch-linux-triage.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Farch-linux-triage.prompt.md) | Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices. |
|
||||
| [ASP.NET .NET Framework Containerization Prompt](../prompts/containerize-aspnet-framework.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcontainerize-aspnet-framework.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcontainerize-aspnet-framework.prompt.md) | Containerize an ASP.NET .NET Framework project by creating Dockerfile and .dockerfile files customized for the project. |
|
||||
| [ASP.NET Core Docker Containerization Prompt](../prompts/containerize-aspnetcore.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcontainerize-aspnetcore.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcontainerize-aspnetcore.prompt.md) | Containerize an ASP.NET Core project by creating Dockerfile and .dockerfile files customized for the project. |
|
||||
| [ASP.NET Minimal API with OpenAPI](../prompts/aspnet-minimal-api-openapi.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Faspnet-minimal-api-openapi.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Faspnet-minimal-api-openapi.prompt.md) | Create ASP.NET Minimal API endpoints with proper OpenAPI documentation |
|
||||
| [Automating Filling in a Form with Playwright MCP](../prompts/playwright-automation-fill-in-form.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fplaywright-automation-fill-in-form.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fplaywright-automation-fill-in-form.prompt.md) | Automate filling in a form using Playwright MCP |
|
||||
| [Azure Cosmos DB NoSQL Data Modeling Expert System Prompt](../prompts/cosmosdb-datamodeling.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcosmosdb-datamodeling.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcosmosdb-datamodeling.prompt.md) | Step-by-step guide for capturing key application requirements for NoSQL use-case and produce Azure Cosmos DB Data NoSQL Model design using best practices and common patterns, artifacts_produced: "cosmosdb_requirements.md" file and "cosmosdb_data_model.md" file |
|
||||
| [Azure Cost Optimize](../prompts/az-cost-optimize.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Faz-cost-optimize.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Faz-cost-optimize.prompt.md) | Analyze Azure resources used in the app (IaC files and/or resources in a target rg) and optimize costs - creating GitHub issues for identified optimizations. |
|
||||
| [Azure Resource Health & Issue Diagnosis](../prompts/azure-resource-health-diagnose.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fazure-resource-health-diagnose.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fazure-resource-health-diagnose.prompt.md) | Analyze Azure resource health, diagnose issues from logs and telemetry, and create a remediation plan for identified problems. |
|
||||
| [Boost Prompt](../prompts/boost-prompt.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fboost-prompt.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fboost-prompt.prompt.md) | Interactive prompt refinement workflow: interrogates scope, deliverables, constraints; copies final markdown to clipboard; never writes code. Requires the Joyride extension. |
|
||||
| [C# Async Programming Best Practices](../prompts/csharp-async.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-async.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-async.prompt.md) | Get best practices for C# async programming |
|
||||
| [C# Documentation Best Practices](../prompts/csharp-docs.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-docs.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-docs.prompt.md) | Ensure that C# types are documented with XML comments and follow best practices for documentation. |
|
||||
| [CentOS Linux Triage](../prompts/centos-linux-triage.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcentos-linux-triage.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcentos-linux-triage.prompt.md) | Triage and resolve CentOS issues using RHEL-compatible tooling, SELinux-aware practices, and firewalld. |
|
||||
| [Code Exemplars Blueprint Generator](../prompts/code-exemplars-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcode-exemplars-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcode-exemplars-blueprint-generator.prompt.md) | Technology-agnostic prompt generator that creates customizable AI prompts for scanning codebases and identifying high-quality code exemplars. Supports multiple programming languages (.NET, Java, JavaScript, TypeScript, React, Angular, Python) with configurable analysis depth, categorization methods, and documentation formats to establish coding standards and maintain consistency across development teams. |
|
||||
| [Comment Code Generate A Tutorial](../prompts/comment-code-generate-a-tutorial.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcomment-code-generate-a-tutorial.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcomment-code-generate-a-tutorial.prompt.md) | Transform this Python script into a polished, beginner-friendly project by refactoring the code, adding clear instructional comments, and generating a complete markdown tutorial. |
|
||||
| [Comprehensive Project Architecture Blueprint Generator](../prompts/architecture-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Farchitecture-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Farchitecture-blueprint-generator.prompt.md) | Comprehensive project architecture blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks and architectural patterns, generates visual diagrams, documents implementation patterns, and provides extensible blueprints for maintaining architectural consistency and guiding new development. |
|
||||
| [Comprehensive Technology Stack Blueprint Generator](../prompts/technology-stack-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ftechnology-stack-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ftechnology-stack-blueprint-generator.prompt.md) | Comprehensive technology stack blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks, programming languages, and implementation patterns across multiple platforms (.NET, Java, JavaScript, React, Python). Generates configurable blueprints with version information, licensing details, usage patterns, coding conventions, and visual diagrams. Provides implementation-ready templates and maintains architectural consistency for guided development. |
|
||||
| [Context Map](../prompts/context-map.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcontext-map.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcontext-map.prompt.md) | Generate a map of all files relevant to a task before making changes |
|
||||
| [Conventional Commit](../prompts/conventional-commit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fconventional-commit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fconventional-commit.prompt.md) | Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation. |
|
||||
| [Convert Plaintext Documentation to Markdown](../prompts/convert-plaintext-to-md.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fconvert-plaintext-to-md.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fconvert-plaintext-to-md.prompt.md) | Convert a text-based document to markdown following instructions from prompt, or if a documented option is passed, follow the instructions for that option. |
|
||||
| [Copilot Instructions Blueprint Generator](../prompts/copilot-instructions-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcopilot-instructions-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcopilot-instructions-blueprint-generator.prompt.md) | Technology-agnostic blueprint generator for creating comprehensive copilot-instructions.md files that guide GitHub Copilot to produce code consistent with project standards, architecture patterns, and exact technology versions by analyzing existing codebase patterns and avoiding assumptions. |
|
||||
| [Create Architectural Decision Record](../prompts/create-architectural-decision-record.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-architectural-decision-record.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-architectural-decision-record.prompt.md) | Create an Architectural Decision Record (ADR) document for AI-optimized decision documentation. |
|
||||
| [Create GitHub Actions Workflow Specification](../prompts/create-github-action-workflow-specification.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-github-action-workflow-specification.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-github-action-workflow-specification.prompt.md) | Create a formal specification for an existing GitHub Actions CI/CD workflow, optimized for AI consumption and workflow maintenance. |
|
||||
| [Create GitHub Issue from Implementation Plan](../prompts/create-github-issues-feature-from-implementation-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-github-issues-feature-from-implementation-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-github-issues-feature-from-implementation-plan.prompt.md) | Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates. |
|
||||
| [Create GitHub Issue from Specification](../prompts/create-github-issue-feature-from-specification.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-github-issue-feature-from-specification.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-github-issue-feature-from-specification.prompt.md) | Create GitHub Issue for feature request from specification file using feature_request.yml template. |
|
||||
| [Create GitHub Issues for Unmet Specification Requirements](../prompts/create-github-issues-for-unmet-specification-requirements.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-github-issues-for-unmet-specification-requirements.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-github-issues-for-unmet-specification-requirements.prompt.md) | Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template. |
|
||||
| [Create GitHub Pull Request from Specification](../prompts/create-github-pull-request-from-specification.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-github-pull-request-from-specification.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-github-pull-request-from-specification.prompt.md) | Create GitHub Pull Request for feature request from specification file using pull_request_template.md template. |
|
||||
| [Create high‑quality AGENTS.md file](../prompts/create-agentsmd.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-agentsmd.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-agentsmd.prompt.md) | Prompt for generating an AGENTS.md file for a repository |
|
||||
| [Create Implementation Plan](../prompts/create-implementation-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-implementation-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-implementation-plan.prompt.md) | Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure. |
|
||||
| [Create LLMs.txt File from Repository Structure](../prompts/create-llms.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-llms.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-llms.prompt.md) | Create an llms.txt file from scratch based on repository structure following the llms.txt specification at https://llmstxt.org/ |
|
||||
| [Create Readme](../prompts/create-readme.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-readme.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-readme.prompt.md) | Create a README.md file for the project |
|
||||
| [Create Specification](../prompts/create-specification.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-specification.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-specification.prompt.md) | Create a new specification file for the solution, optimized for Generative AI consumption. |
|
||||
| [Create Spring Boot Java project prompt](../prompts/create-spring-boot-java-project.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-spring-boot-java-project.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-spring-boot-java-project.prompt.md) | Create Spring Boot Java Project Skeleton |
|
||||
| [Create Spring Boot Kotlin project prompt](../prompts/create-spring-boot-kotlin-project.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-spring-boot-kotlin-project.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-spring-boot-kotlin-project.prompt.md) | Create Spring Boot Kotlin Project Skeleton |
|
||||
| [Create Technical Spike Document](../prompts/create-technical-spike.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-technical-spike.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-technical-spike.prompt.md) | Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation. |
|
||||
| [Create TLDR Page](../prompts/create-tldr-page.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-tldr-page.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-tldr-page.prompt.md) | Create a tldr page from documentation URLs and command examples, requiring both URL and command name. |
|
||||
| [Create TypeSpec API Plugin](../prompts/typespec-create-api-plugin.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ftypespec-create-api-plugin.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ftypespec-create-api-plugin.prompt.md) | Generate a TypeSpec API plugin with REST operations, authentication, and Adaptive Cards for Microsoft 365 Copilot |
|
||||
| [Create TypeSpec Declarative Agent](../prompts/typespec-create-agent.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ftypespec-create-agent.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ftypespec-create-agent.prompt.md) | Generate a complete TypeSpec declarative agent with instructions, capabilities, and conversation starters for Microsoft 365 Copilot |
|
||||
| [Dataverse Python Production Code Generator](../prompts/dataverse-python-production-code.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdataverse-python-production-code.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdataverse-python-production-code.prompt.md) | Generate production-ready Python code using Dataverse SDK with error handling, optimization, and best practices |
|
||||
| [Dataverse Python Use Case Solution Builder](../prompts/dataverse-python-usecase-builder.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdataverse-python-usecase-builder.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdataverse-python-usecase-builder.prompt.md) | Generate complete solutions for specific Dataverse SDK use cases with architecture recommendations |
|
||||
| [Dataverse Python Advanced Patterns](../prompts/dataverse-python-advanced-patterns.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdataverse-python-advanced-patterns.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdataverse-python-advanced-patterns.prompt.md) | Generate production code for Dataverse SDK using advanced patterns, error handling, and optimization techniques. |
|
||||
| [Dataverse Python Quickstart Generator](../prompts/dataverse-python-quickstart.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdataverse-python-quickstart.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdataverse-python-quickstart.prompt.md) | Generate Python SDK setup + CRUD + bulk + paging snippets using official patterns. |
|
||||
| [Debian Linux Triage](../prompts/debian-linux-triage.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdebian-linux-triage.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdebian-linux-triage.prompt.md) | Triage and resolve Debian Linux issues with apt, systemd, and AppArmor-aware guidance. |
|
||||
| [DevOps Rollout Plan Generator](../prompts/devops-rollout-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdevops-rollout-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdevops-rollout-plan.prompt.md) | Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes |
|
||||
| [Diátaxis Documentation Expert](../prompts/documentation-writer.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdocumentation-writer.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdocumentation-writer.prompt.md) | 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. |
|
||||
| [EditorConfig Expert](../prompts/editorconfig.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Feditorconfig.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Feditorconfig.prompt.md) | Generates a comprehensive and best-practice-oriented .editorconfig file based on project analysis and user preferences. |
|
||||
| [Entity Framework Core Best Practices](../prompts/ef-core.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fef-core.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fef-core.prompt.md) | Get best practices for Entity Framework Core |
|
||||
| [Epic Architecture Specification Prompt](../prompts/breakdown-epic-arch.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-epic-arch.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-epic-arch.prompt.md) | Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document. |
|
||||
| [Epic Product Requirements Document (PRD) Prompt](../prompts/breakdown-epic-pm.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-epic-pm.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-epic-pm.prompt.md) | Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification. |
|
||||
| [Feature Implementation Plan Prompt](../prompts/breakdown-feature-implementation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-feature-implementation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-feature-implementation.prompt.md) | Prompt for creating detailed feature implementation plans, following Epoch monorepo structure. |
|
||||
| [Feature PRD Prompt](../prompts/breakdown-feature-prd.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-feature-prd.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-feature-prd.prompt.md) | Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic. |
|
||||
| [Fedora Linux Triage](../prompts/fedora-linux-triage.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ffedora-linux-triage.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ffedora-linux-triage.prompt.md) | Triage and resolve Fedora issues with dnf, systemd, and SELinux-aware guidance. |
|
||||
| [Finalize Agent Prompt](../prompts/finalize-agent-prompt.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ffinalize-agent-prompt.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ffinalize-agent-prompt.prompt.md) | Finalize prompt file using the role of an AI agent to polish the prompt for the end user. |
|
||||
| [Generate Application from OpenAPI Spec](../prompts/openapi-to-application-code.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fopenapi-to-application-code.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fopenapi-to-application-code.prompt.md) | Generate a complete, production-ready application from an OpenAPI specification |
|
||||
| [Generate C# MCP Server](../prompts/csharp-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-mcp-server-generator.prompt.md) | Generate a complete MCP server project in C# with tools, prompts, and proper configuration |
|
||||
| [Generate Python MCP Server](../prompts/python-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpython-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpython-mcp-server-generator.prompt.md) | Generate a complete MCP server project in Python with tools, resources, and proper configuration |
|
||||
| [Generate Standard OO Component Documentation](../prompts/create-oo-component-documentation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-oo-component-documentation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcreate-oo-component-documentation.prompt.md) | Create comprehensive, standardized documentation for object-oriented components following industry best practices and architectural documentation standards. |
|
||||
| [Generate TypeScript MCP Server](../prompts/typescript-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ftypescript-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ftypescript-mcp-server-generator.prompt.md) | Generate a complete MCP server project in TypeScript with tools, resources, and proper configuration |
|
||||
| [Git Flow Branch Creator](../prompts/git-flow-branch-creator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fgit-flow-branch-creator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fgit-flow-branch-creator.prompt.md) | Intelligent Git Flow branch creator that analyzes git status/diff and creates appropriate branches following the nvie Git Flow branching model. |
|
||||
| [Github Copilot Starter](../prompts/github-copilot-starter.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fgithub-copilot-starter.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fgithub-copilot-starter.prompt.md) | Set up complete GitHub Copilot configuration for a new project based on technology stack |
|
||||
| [GitHub Issue Planning & Project Automation Prompt](../prompts/breakdown-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-plan.prompt.md) | Issue Planning and Automation prompt that generates comprehensive project plans with Epic > Feature > Story/Enabler > Test hierarchy, dependencies, priorities, and automated tracking. |
|
||||
| [Go MCP Server Project Generator](../prompts/go-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fgo-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fgo-mcp-server-generator.prompt.md) | Generate a complete Go MCP server project with proper structure, dependencies, and implementation using the official github.com/modelcontextprotocol/go-sdk. |
|
||||
| [GraalVM Native Image Agent](../prompts/java-add-graalvm-native-image-support.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-add-graalvm-native-image-support.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-add-graalvm-native-image-support.prompt.md) | GraalVM Native Image expert that adds native image support to Java applications, builds the project, analyzes build errors, applies fixes, and iterates until successful compilation using Oracle best practices. |
|
||||
| [Interactive Programming Nudge](../prompts/remember-interactive-programming.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fremember-interactive-programming.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fremember-interactive-programming.prompt.md) | A micro-prompt that reminds the agent that it is an interactive programmer. Works great in Clojure when Copilot has access to the REPL (probably via Backseat Driver). Will work with any system that has a live REPL that the agent can use. Adapt the prompt with any specific reminders in your workflow and/or workspace. |
|
||||
| [Java Documentation (Javadoc) Best Practices](../prompts/java-docs.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-docs.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-docs.prompt.md) | Ensure that Java types are documented with Javadoc comments and follow best practices for documentation. |
|
||||
| [Java MCP Server Generator](../prompts/java-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-mcp-server-generator.prompt.md) | Generate a complete Model Context Protocol server project in Java using the official MCP Java SDK with reactive streams and optional Spring Boot integration. |
|
||||
| [Javascript Typescript Jest](../prompts/javascript-typescript-jest.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjavascript-typescript-jest.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjavascript-typescript-jest.prompt.md) | Best practices for writing JavaScript/TypeScript tests using Jest, including mocking strategies, test structure, and common patterns. |
|
||||
| [JUnit 5+ Best Practices](../prompts/java-junit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-junit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-junit.prompt.md) | Get best practices for JUnit 5 unit testing, including data-driven tests |
|
||||
| [Kotlin MCP Server Project Generator](../prompts/kotlin-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fkotlin-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fkotlin-mcp-server-generator.prompt.md) | Generate a complete Kotlin MCP server project with proper structure, dependencies, and implementation using the official io.modelcontextprotocol:kotlin-sdk library. |
|
||||
| [Mcp Create Adaptive Cards](../prompts/mcp-create-adaptive-cards.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmcp-create-adaptive-cards.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmcp-create-adaptive-cards.prompt.md) | | |
|
||||
| [Mcp Create Declarative Agent](../prompts/mcp-create-declarative-agent.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmcp-create-declarative-agent.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmcp-create-declarative-agent.prompt.md) | | |
|
||||
| [Mcp Deploy Manage Agents](../prompts/mcp-deploy-manage-agents.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmcp-deploy-manage-agents.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmcp-deploy-manage-agents.prompt.md) | | |
|
||||
| [Memory Keeper](../prompts/remember.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fremember.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fremember.prompt.md) | Transforms lessons learned into domain-organized memory instructions (global or workspace). Syntax: `/remember [>domain [scope]] lesson clue` where scope is `global` (default), `user`, `workspace`, or `ws`. |
|
||||
| [Memory Merger](../prompts/memory-merger.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmemory-merger.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmemory-merger.prompt.md) | Merges mature lessons from a domain memory file into its instruction file. Syntax: `/memory-merger >domain [scope]` where scope is `global` (default), `user`, `workspace`, or `ws`. |
|
||||
| [Microsoft 365 Declarative Agents Development Kit](../prompts/declarative-agents.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdeclarative-agents.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fdeclarative-agents.prompt.md) | Complete development kit for Microsoft 365 Copilot declarative agents with three comprehensive workflows (basic, advanced, validation), TypeSpec support, and Microsoft 365 Agents Toolkit integration |
|
||||
| [Migration and Code Evolution Instructions Generator](../prompts/generate-custom-instructions-from-codebase.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fgenerate-custom-instructions-from-codebase.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fgenerate-custom-instructions-from-codebase.prompt.md) | Migration and code evolution instructions generator for GitHub Copilot. Analyzes differences between two project versions (branches, commits, or releases) to create precise instructions allowing Copilot to maintain consistency during technology migrations, major refactoring, or framework version upgrades. |
|
||||
| [MkDocs AI Translator](../prompts/mkdocs-translations.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmkdocs-translations.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmkdocs-translations.prompt.md) | Generate a language translation for a mkdocs documentation stack. |
|
||||
| [MSTest Best Practices (MSTest 3.x/4.x)](../prompts/csharp-mstest.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-mstest.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-mstest.prompt.md) | Get best practices for MSTest 3.x/4.x unit testing, including modern assertion APIs and data-driven tests |
|
||||
| [Multi Stage Dockerfile](../prompts/multi-stage-dockerfile.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmulti-stage-dockerfile.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmulti-stage-dockerfile.prompt.md) | Create optimized multi-stage Dockerfiles for any language or framework |
|
||||
| [My Issues](../prompts/my-issues.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmy-issues.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmy-issues.prompt.md) | List my issues in the current repository |
|
||||
| [My Pull Requests](../prompts/my-pull-requests.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmy-pull-requests.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmy-pull-requests.prompt.md) | List my pull requests in the current repository |
|
||||
| [Next Intl Add Language](../prompts/next-intl-add-language.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fnext-intl-add-language.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fnext-intl-add-language.prompt.md) | Add new language to a Next.js + next-intl application |
|
||||
| [NUnit Best Practices](../prompts/csharp-nunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-nunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-nunit.prompt.md) | Get best practices for NUnit unit testing, including data-driven tests |
|
||||
| [PHP MCP Server Generator](../prompts/php-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fphp-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fphp-mcp-server-generator.prompt.md) | Generate a complete PHP Model Context Protocol server project with tools, resources, prompts, and tests using the official PHP SDK |
|
||||
| [PostgreSQL Code Review Assistant](../prompts/postgresql-code-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpostgresql-code-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpostgresql-code-review.prompt.md) | PostgreSQL-specific code review assistant focusing on PostgreSQL best practices, anti-patterns, and unique quality standards. Covers JSONB operations, array usage, custom types, schema design, function optimization, and PostgreSQL-exclusive security features like Row Level Security (RLS). |
|
||||
| [PostgreSQL Development Assistant](../prompts/postgresql-optimization.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpostgresql-optimization.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpostgresql-optimization.prompt.md) | PostgreSQL-specific development assistant focusing on unique PostgreSQL features, advanced data types, and PostgreSQL-exclusive capabilities. Covers JSONB operations, array types, custom types, range/geometric types, full-text search, window functions, and PostgreSQL extensions ecosystem. |
|
||||
| [Power Apps Code Apps Project Scaffolding](../prompts/power-apps-code-app-scaffold.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpower-apps-code-app-scaffold.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpower-apps-code-app-scaffold.prompt.md) | Scaffold a complete Power Apps Code App project with PAC CLI setup, SDK integration, and connector configuration |
|
||||
| [Power BI Data Model Design Review](../prompts/power-bi-model-design-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpower-bi-model-design-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpower-bi-model-design-review.prompt.md) | Comprehensive Power BI data model design review prompt for evaluating model architecture, relationships, and optimization opportunities. |
|
||||
| [Power BI DAX Formula Optimizer](../prompts/power-bi-dax-optimization.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpower-bi-dax-optimization.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpower-bi-dax-optimization.prompt.md) | Comprehensive Power BI DAX formula optimization prompt for improving performance, readability, and maintainability of DAX calculations. |
|
||||
| [Power BI Performance Troubleshooting Guide](../prompts/power-bi-performance-troubleshooting.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpower-bi-performance-troubleshooting.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpower-bi-performance-troubleshooting.prompt.md) | Systematic Power BI performance troubleshooting prompt for identifying, diagnosing, and resolving performance issues in Power BI models, reports, and queries. |
|
||||
| [Power BI Report Visualization Designer](../prompts/power-bi-report-design-consultation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpower-bi-report-design-consultation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpower-bi-report-design-consultation.prompt.md) | Power BI report visualization design prompt for creating effective, user-friendly, and accessible reports with optimal chart selection and layout design. |
|
||||
| [Power Platform MCP Connector Generator](../prompts/mcp-copilot-studio-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmcp-copilot-studio-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fmcp-copilot-studio-server-generator.prompt.md) | Generate a complete MCP server implementation optimized for Copilot Studio integration with proper schema constraints and streamable HTTP support |
|
||||
| [Power Platform MCP Connector Suite](../prompts/power-platform-mcp-connector-suite.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpower-platform-mcp-connector-suite.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpower-platform-mcp-connector-suite.prompt.md) | Generate complete Power Platform custom connector with MCP integration for Copilot Studio - includes schema generation, troubleshooting, and validation |
|
||||
| [Product Manager Assistant: Feature Identification and Specification](../prompts/gen-specs-as-issues.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fgen-specs-as-issues.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fgen-specs-as-issues.prompt.md) | This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation. |
|
||||
| [Professional Prompt Builder](../prompts/prompt-builder.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fprompt-builder.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fprompt-builder.prompt.md) | Guide users through creating high-quality GitHub Copilot prompts with proper structure, tools, and best practices. |
|
||||
| [Project Folder Structure Blueprint Generator](../prompts/folder-structure-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ffolder-structure-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ffolder-structure-blueprint-generator.prompt.md) | Comprehensive technology-agnostic prompt for analyzing and documenting project folder structures. Auto-detects project types (.NET, Java, React, Angular, Python, Node.js, Flutter), generates detailed blueprints with visualization options, naming conventions, file placement patterns, and extension templates for maintaining consistent code organization across diverse technology stacks. |
|
||||
| [Project Workflow Documentation Generator](../prompts/project-workflow-analysis-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fproject-workflow-analysis-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fproject-workflow-analysis-blueprint-generator.prompt.md) | Comprehensive technology-agnostic prompt generator for documenting end-to-end application workflows. Automatically detects project architecture patterns, technology stacks, and data flow patterns to generate detailed implementation blueprints covering entry points, service layers, data access, error handling, and testing approaches across multiple technologies including .NET, Java/Spring, React, and microservices architectures. |
|
||||
| [Pytest Coverage](../prompts/pytest-coverage.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpytest-coverage.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fpytest-coverage.prompt.md) | Run pytest tests with coverage, discover lines missing coverage, and increase coverage to 100%. |
|
||||
| [README Generator Prompt](../prompts/readme-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freadme-blueprint-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freadme-blueprint-generator.prompt.md) | Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans .github/copilot directory files and copilot-instructions.md to extract project information, technology stack, architecture, development workflow, coding standards, and testing approaches while generating well-structured markdown documentation with proper formatting, cross-references, and developer-focused content. |
|
||||
| [Refactor Method Complexity Reduce](../prompts/refactor-method-complexity-reduce.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frefactor-method-complexity-reduce.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frefactor-method-complexity-reduce.prompt.md) | Refactor given method `${input:methodName}` to reduce its cognitive complexity to `${input:complexityThreshold}` or below, by extracting helper methods. |
|
||||
| [Refactor Plan](../prompts/refactor-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frefactor-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frefactor-plan.prompt.md) | Plan a multi-file refactor with proper sequencing and rollback steps |
|
||||
| [Refactoring Java Methods with Extract Method](../prompts/java-refactoring-extract-method.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-refactoring-extract-method.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-refactoring-extract-method.prompt.md) | Refactoring using Extract Methods in Java Language |
|
||||
| [Refactoring Java Methods with Remove Parameter](../prompts/java-refactoring-remove-parameter.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-refactoring-remove-parameter.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-refactoring-remove-parameter.prompt.md) | Refactoring using Remove Parameter in Java Language |
|
||||
| [Repo Story Time](../prompts/repo-story-time.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frepo-story-time.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frepo-story-time.prompt.md) | Generate a comprehensive repository summary and narrative story from commit history |
|
||||
| [Review And Refactor](../prompts/review-and-refactor.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freview-and-refactor.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Freview-and-refactor.prompt.md) | Review and refactor code in your project according to defined instructions |
|
||||
| [Ruby MCP Server Generator](../prompts/ruby-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fruby-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fruby-mcp-server-generator.prompt.md) | Generate a complete Model Context Protocol server project in Ruby using the official MCP Ruby SDK gem. |
|
||||
| [Rust Mcp Server Generator](../prompts/rust-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frust-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Frust-mcp-server-generator.prompt.md) | Generate a complete Rust Model Context Protocol server project with tools, prompts, resources, and tests using the official rmcp SDK |
|
||||
| [Sa Generate](../prompts/structured-autonomy-generate.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-generate.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-generate.prompt.md) | Structured Autonomy Implementation Generator Prompt |
|
||||
| [Sa Implement](../prompts/structured-autonomy-implement.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-implement.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-implement.prompt.md) | Structured Autonomy Implementation Prompt |
|
||||
| [Sa Plan](../prompts/structured-autonomy-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fstructured-autonomy-plan.prompt.md) | Structured Autonomy Planning Prompt |
|
||||
| [Shuffle JSON Data](../prompts/shuffle-json-data.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fshuffle-json-data.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fshuffle-json-data.prompt.md) | Shuffle repetitive JSON objects safely by validating schema consistency before randomising entries. |
|
||||
| [Spring Boot Best Practices](../prompts/java-springboot.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-springboot.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fjava-springboot.prompt.md) | Get best practices for developing applications with Spring Boot. |
|
||||
| [Spring Boot with Kotlin Best Practices](../prompts/kotlin-springboot.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fkotlin-springboot.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fkotlin-springboot.prompt.md) | Get best practices for developing applications with Spring Boot and Kotlin. |
|
||||
| [SQL Code Review](../prompts/sql-code-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsql-code-review.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsql-code-review.prompt.md) | Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Focuses on SQL injection prevention, access control, code standards, and anti-pattern detection. Complements SQL optimization prompt for complete development coverage. |
|
||||
| [SQL Performance Optimization Assistant](../prompts/sql-optimization.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsql-optimization.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsql-optimization.prompt.md) | Universal SQL performance optimization assistant for comprehensive query tuning, indexing strategies, and database performance analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Provides execution plan analysis, pagination optimization, batch operations, and performance monitoring guidance. |
|
||||
| [Suggest Awesome GitHub Copilot Custom Agents](../prompts/suggest-awesome-github-copilot-agents.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsuggest-awesome-github-copilot-agents.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsuggest-awesome-github-copilot-agents.prompt.md) | 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, and identifying outdated agents that need updates. |
|
||||
| [Suggest Awesome GitHub Copilot Instructions](../prompts/suggest-awesome-github-copilot-instructions.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsuggest-awesome-github-copilot-instructions.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsuggest-awesome-github-copilot-instructions.prompt.md) | 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, and identifying outdated instructions that need updates. |
|
||||
| [Suggest Awesome GitHub Copilot Prompts](../prompts/suggest-awesome-github-copilot-prompts.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsuggest-awesome-github-copilot-prompts.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsuggest-awesome-github-copilot-prompts.prompt.md) | 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, and identifying outdated prompts that need updates. |
|
||||
| [Suggest Awesome GitHub Copilot Skills](../prompts/suggest-awesome-github-copilot-skills.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsuggest-awesome-github-copilot-skills.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fsuggest-awesome-github-copilot-skills.prompt.md) | Suggest relevant GitHub Copilot skills from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing skills in this repository, and identifying outdated skills that need updates. |
|
||||
| [Swift MCP Server Generator](../prompts/swift-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fswift-mcp-server-generator.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fswift-mcp-server-generator.prompt.md) | Generate a complete Model Context Protocol server project in Swift using the official MCP Swift SDK package. |
|
||||
| [Test Generation with Playwright MCP](../prompts/playwright-generate-test.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fplaywright-generate-test.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fplaywright-generate-test.prompt.md) | Generate a Playwright test based on a scenario using Playwright MCP |
|
||||
| [Test Planning & Quality Assurance Prompt](../prompts/breakdown-test.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-test.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fbreakdown-test.prompt.md) | Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for GitHub projects. |
|
||||
| [TLDR Prompt](../prompts/tldr-prompt.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ftldr-prompt.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Ftldr-prompt.prompt.md) | Create tldr summaries for GitHub Copilot files (prompts, agents, instructions, collections), MCP servers, or documentation from URLs and queries. |
|
||||
| [TUnit Best Practices](../prompts/csharp-tunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-tunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-tunit.prompt.md) | Get best practices for TUnit unit testing, including data-driven tests |
|
||||
| [Update Azure Verified Modules in Bicep Files](../prompts/update-avm-modules-in-bicep.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fupdate-avm-modules-in-bicep.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fupdate-avm-modules-in-bicep.prompt.md) | Update Azure Verified Modules (AVM) to latest versions in Bicep files. |
|
||||
| [Update Implementation Plan](../prompts/update-implementation-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fupdate-implementation-plan.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fupdate-implementation-plan.prompt.md) | 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. |
|
||||
| [Update LLMs.txt File](../prompts/update-llms.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fupdate-llms.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fupdate-llms.prompt.md) | 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/ |
|
||||
| [Update Markdown File Index](../prompts/update-markdown-file-index.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fupdate-markdown-file-index.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fupdate-markdown-file-index.prompt.md) | Update a markdown file section with an index/table of files from a specified folder. |
|
||||
| [Update Specification](../prompts/update-specification.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fupdate-specification.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fupdate-specification.prompt.md) | Update an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code. |
|
||||
| [Update Standard OO Component Documentation](../prompts/update-oo-component-documentation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fupdate-oo-component-documentation.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fupdate-oo-component-documentation.prompt.md) | Update existing object-oriented component documentation following industry best practices and architectural documentation standards. |
|
||||
| [Website Exploration for Testing](../prompts/playwright-explore-website.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fplaywright-explore-website.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fplaywright-explore-website.prompt.md) | Website exploration for testing using Playwright MCP |
|
||||
| [What Context Do You Need?](../prompts/what-context-needed.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fwhat-context-needed.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fwhat-context-needed.prompt.md) | Ask Copilot what files it needs to see before answering a question |
|
||||
| [Write Coding Standards From File](../prompts/write-coding-standards-from-file.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fwrite-coding-standards-from-file.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fwrite-coding-standards-from-file.prompt.md) | 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. |
|
||||
| [XUnit Best Practices](../prompts/csharp-xunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-xunit.prompt.md)<br />[](https://aka.ms/awesome-copilot/install/prompt?url=vscode-insiders%3Achat-prompt%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fprompts%2Fcsharp-xunit.prompt.md) | Get best practices for XUnit unit testing, including data-driven tests |
|
||||
@@ -3,6 +3,10 @@
|
||||
Agent Skills are self-contained folders with instructions and bundled resources that enhance AI capabilities for specialized tasks. Based on the [Agent Skills specification](https://agentskills.io/specification), each skill contains a `SKILL.md` file with detailed instructions that agents load on-demand.
|
||||
|
||||
Skills differ from other primitives by supporting bundled assets (scripts, code samples, reference data) that agents can utilize when performing specialized tasks.
|
||||
### How to Contribute
|
||||
|
||||
See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to contribute new agent skills, improve existing ones, and share your use cases.
|
||||
|
||||
### How to Use Agent Skills
|
||||
|
||||
**What's Included:**
|
||||
@@ -22,54 +26,201 @@ Skills differ from other primitives by supporting bundled assets (scripts, code
|
||||
|
||||
| Name | Description | Bundled Assets |
|
||||
| ---- | ----------- | -------------- |
|
||||
| [add-educational-comments](../skills/add-educational-comments/SKILL.md) | Add educational comments to the file specified, or prompt asking for file to comment if one is not provided. | None |
|
||||
| [agent-governance](../skills/agent-governance/SKILL.md) | Patterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when:<br />- Building AI agents that call external tools (APIs, databases, file systems)<br />- Implementing policy-based access controls for agent tool usage<br />- Adding semantic intent classification to detect dangerous prompts<br />- Creating trust scoring systems for multi-agent workflows<br />- Building audit trails for agent actions and decisions<br />- Enforcing rate limits, content filters, or tool restrictions on agents<br />- Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen) | None |
|
||||
| [agentic-eval](../skills/agentic-eval/SKILL.md) | Patterns and techniques for evaluating and improving AI agent outputs. Use this skill when:<br />- Implementing self-critique and reflection loops<br />- Building evaluator-optimizer pipelines for quality-critical generation<br />- Creating test-driven code refinement workflows<br />- Designing rubric-based or LLM-as-judge evaluation systems<br />- Adding iterative improvement to agent outputs (code, reports, analysis)<br />- Measuring and improving agent response quality | None |
|
||||
| [ai-prompt-engineering-safety-review](../skills/ai-prompt-engineering-safety-review/SKILL.md) | Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations with extensive frameworks, testing methodologies, and educational content. | None |
|
||||
| [appinsights-instrumentation](../skills/appinsights-instrumentation/SKILL.md) | Instrument a webapp to send useful telemetry data to Azure App Insights | `LICENSE.txt`<br />`examples/appinsights.bicep`<br />`references/ASPNETCORE.md`<br />`references/AUTO.md`<br />`references/NODEJS.md`<br />`references/PYTHON.md`<br />`scripts/appinsights.ps1` |
|
||||
| [apple-appstore-reviewer](../skills/apple-appstore-reviewer/SKILL.md) | Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons. | None |
|
||||
| [arch-linux-triage](../skills/arch-linux-triage/SKILL.md) | Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices. | None |
|
||||
| [architecture-blueprint-generator](../skills/architecture-blueprint-generator/SKILL.md) | Comprehensive project architecture blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks and architectural patterns, generates visual diagrams, documents implementation patterns, and provides extensible blueprints for maintaining architectural consistency and guiding new development. | None |
|
||||
| [aspire](../skills/aspire/SKILL.md) | Aspire skill covering the Aspire CLI, AppHost orchestration, service discovery, integrations, MCP server, VS Code extension, Dev Containers, GitHub Codespaces, templates, dashboard, and deployment. Use when the user asks to create, run, debug, configure, deploy, or troubleshoot an Aspire distributed application. | `references/architecture.md`<br />`references/cli-reference.md`<br />`references/dashboard.md`<br />`references/deployment.md`<br />`references/integrations-catalog.md`<br />`references/mcp-server.md`<br />`references/polyglot-apis.md`<br />`references/testing.md`<br />`references/troubleshooting.md` |
|
||||
| [aspnet-minimal-api-openapi](../skills/aspnet-minimal-api-openapi/SKILL.md) | Create ASP.NET Minimal API endpoints with proper OpenAPI documentation | None |
|
||||
| [az-cost-optimize](../skills/az-cost-optimize/SKILL.md) | Analyze Azure resources used in the app (IaC files and/or resources in a target rg) and optimize costs - creating GitHub issues for identified optimizations. | None |
|
||||
| [azure-deployment-preflight](../skills/azure-deployment-preflight/SKILL.md) | Performs comprehensive preflight validation of Bicep deployments to Azure, including template syntax validation, what-if analysis, and permission checks. Use this skill before any deployment to Azure to preview changes, identify potential issues, and ensure the deployment will succeed. Activate when users mention deploying to Azure, validating Bicep files, checking deployment permissions, previewing infrastructure changes, running what-if, or preparing for azd provision. | `references/ERROR-HANDLING.md`<br />`references/REPORT-TEMPLATE.md`<br />`references/VALIDATION-COMMANDS.md` |
|
||||
| [azure-devops-cli](../skills/azure-devops-cli/SKILL.md) | Manage Azure DevOps resources via CLI including projects, repos, pipelines, builds, pull requests, work items, artifacts, and service endpoints. Use when working with Azure DevOps, az commands, devops automation, CI/CD, or when user mentions Azure DevOps CLI. | None |
|
||||
| [azure-resource-health-diagnose](../skills/azure-resource-health-diagnose/SKILL.md) | Analyze Azure resource health, diagnose issues from logs and telemetry, and create a remediation plan for identified problems. | None |
|
||||
| [azure-resource-visualizer](../skills/azure-resource-visualizer/SKILL.md) | Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. Use this skill when the user asks for a diagram of their Azure resources or help in understanding how the resources relate to each other. | `LICENSE.txt`<br />`assets/template-architecture.md` |
|
||||
| [azure-role-selector](../skills/azure-role-selector/SKILL.md) | When user is asking for guidance for which role to assign to an identity given desired permissions, this agent helps them understand the role that will meet the requirements with least privilege access and how to apply that role. | `LICENSE.txt` |
|
||||
| [azure-static-web-apps](../skills/azure-static-web-apps/SKILL.md) | Helps create, configure, and deploy Azure Static Web Apps using the SWA CLI. Use when deploying static sites to Azure, setting up SWA local development, configuring staticwebapp.config.json, adding Azure Functions APIs to SWA, or setting up GitHub Actions CI/CD for Static Web Apps. | None |
|
||||
| [bigquery-pipeline-audit](../skills/bigquery-pipeline-audit/SKILL.md) | Audits Python + BigQuery pipelines for cost safety, idempotency, and production readiness. Returns a structured report with exact patch locations. | None |
|
||||
| [boost-prompt](../skills/boost-prompt/SKILL.md) | Interactive prompt refinement workflow: interrogates scope, deliverables, constraints; copies final markdown to clipboard; never writes code. Requires the Joyride extension. | None |
|
||||
| [breakdown-epic-arch](../skills/breakdown-epic-arch/SKILL.md) | Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document. | None |
|
||||
| [breakdown-epic-pm](../skills/breakdown-epic-pm/SKILL.md) | Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification. | None |
|
||||
| [breakdown-feature-implementation](../skills/breakdown-feature-implementation/SKILL.md) | Prompt for creating detailed feature implementation plans, following Epoch monorepo structure. | None |
|
||||
| [breakdown-feature-prd](../skills/breakdown-feature-prd/SKILL.md) | Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic. | None |
|
||||
| [breakdown-plan](../skills/breakdown-plan/SKILL.md) | Issue Planning and Automation prompt that generates comprehensive project plans with Epic > Feature > Story/Enabler > Test hierarchy, dependencies, priorities, and automated tracking. | None |
|
||||
| [breakdown-test](../skills/breakdown-test/SKILL.md) | Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for GitHub projects. | None |
|
||||
| [centos-linux-triage](../skills/centos-linux-triage/SKILL.md) | Triage and resolve CentOS issues using RHEL-compatible tooling, SELinux-aware practices, and firewalld. | None |
|
||||
| [chrome-devtools](../skills/chrome-devtools/SKILL.md) | Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance. | None |
|
||||
| [code-exemplars-blueprint-generator](../skills/code-exemplars-blueprint-generator/SKILL.md) | Technology-agnostic prompt generator that creates customizable AI prompts for scanning codebases and identifying high-quality code exemplars. Supports multiple programming languages (.NET, Java, JavaScript, TypeScript, React, Angular, Python) with configurable analysis depth, categorization methods, and documentation formats to establish coding standards and maintain consistency across development teams. | None |
|
||||
| [comment-code-generate-a-tutorial](../skills/comment-code-generate-a-tutorial/SKILL.md) | Transform this Python script into a polished, beginner-friendly project by refactoring the code, adding clear instructional comments, and generating a complete markdown tutorial. | None |
|
||||
| [containerize-aspnet-framework](../skills/containerize-aspnet-framework/SKILL.md) | Containerize an ASP.NET .NET Framework project by creating Dockerfile and .dockerfile files customized for the project. | None |
|
||||
| [containerize-aspnetcore](../skills/containerize-aspnetcore/SKILL.md) | Containerize an ASP.NET Core project by creating Dockerfile and .dockerfile files customized for the project. | None |
|
||||
| [context-map](../skills/context-map/SKILL.md) | Generate a map of all files relevant to a task before making changes | None |
|
||||
| [conventional-commit](../skills/conventional-commit/SKILL.md) | Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation. | None |
|
||||
| [convert-plaintext-to-md](../skills/convert-plaintext-to-md/SKILL.md) | Convert a text-based document to markdown following instructions from prompt, or if a documented option is passed, follow the instructions for that option. | None |
|
||||
| [copilot-cli-quickstart](../skills/copilot-cli-quickstart/SKILL.md) | Use this skill when someone wants to learn GitHub Copilot CLI from scratch. Offers interactive step-by-step tutorials with separate Developer and Non-Developer tracks, plus on-demand Q&A. Just say "start tutorial" or ask a question! Note: This skill targets GitHub Copilot CLI specifically and uses CLI-specific tools (ask_user, sql, fetch_copilot_cli_documentation). | None |
|
||||
| [copilot-instructions-blueprint-generator](../skills/copilot-instructions-blueprint-generator/SKILL.md) | Technology-agnostic blueprint generator for creating comprehensive copilot-instructions.md files that guide GitHub Copilot to produce code consistent with project standards, architecture patterns, and exact technology versions by analyzing existing codebase patterns and avoiding assumptions. | None |
|
||||
| [copilot-sdk](../skills/copilot-sdk/SKILL.md) | Build agentic applications with GitHub Copilot SDK. Use when embedding AI agents in apps, creating custom tools, implementing streaming responses, managing sessions, connecting to MCP servers, or creating custom agents. Triggers on Copilot SDK, GitHub SDK, agentic app, embed Copilot, programmable agent, MCP server, custom agent. | None |
|
||||
| [copilot-usage-metrics](../skills/copilot-usage-metrics/SKILL.md) | Retrieve and display GitHub Copilot usage metrics for organizations and enterprises using the GitHub CLI and REST API. | `get-enterprise-metrics.sh`<br />`get-enterprise-user-metrics.sh`<br />`get-org-metrics.sh`<br />`get-org-user-metrics.sh` |
|
||||
| [cosmosdb-datamodeling](../skills/cosmosdb-datamodeling/SKILL.md) | Step-by-step guide for capturing key application requirements for NoSQL use-case and produce Azure Cosmos DB Data NoSQL Model design using best practices and common patterns, artifacts_produced: "cosmosdb_requirements.md" file and "cosmosdb_data_model.md" file | None |
|
||||
| [create-agentsmd](../skills/create-agentsmd/SKILL.md) | Prompt for generating an AGENTS.md file for a repository | None |
|
||||
| [create-architectural-decision-record](../skills/create-architectural-decision-record/SKILL.md) | Create an Architectural Decision Record (ADR) document for AI-optimized decision documentation. | None |
|
||||
| [create-github-action-workflow-specification](../skills/create-github-action-workflow-specification/SKILL.md) | Create a formal specification for an existing GitHub Actions CI/CD workflow, optimized for AI consumption and workflow maintenance. | None |
|
||||
| [create-github-issue-feature-from-specification](../skills/create-github-issue-feature-from-specification/SKILL.md) | Create GitHub Issue for feature request from specification file using feature_request.yml template. | None |
|
||||
| [create-github-issues-feature-from-implementation-plan](../skills/create-github-issues-feature-from-implementation-plan/SKILL.md) | Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates. | None |
|
||||
| [create-github-issues-for-unmet-specification-requirements](../skills/create-github-issues-for-unmet-specification-requirements/SKILL.md) | Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template. | None |
|
||||
| [create-github-pull-request-from-specification](../skills/create-github-pull-request-from-specification/SKILL.md) | Create GitHub Pull Request for feature request from specification file using pull_request_template.md template. | None |
|
||||
| [create-implementation-plan](../skills/create-implementation-plan/SKILL.md) | Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure. | None |
|
||||
| [create-llms](../skills/create-llms/SKILL.md) | Create an llms.txt file from scratch based on repository structure following the llms.txt specification at https://llmstxt.org/ | None |
|
||||
| [create-oo-component-documentation](../skills/create-oo-component-documentation/SKILL.md) | Create comprehensive, standardized documentation for object-oriented components following industry best practices and architectural documentation standards. | None |
|
||||
| [create-readme](../skills/create-readme/SKILL.md) | Create a README.md file for the project | None |
|
||||
| [create-specification](../skills/create-specification/SKILL.md) | Create a new specification file for the solution, optimized for Generative AI consumption. | None |
|
||||
| [create-spring-boot-java-project](../skills/create-spring-boot-java-project/SKILL.md) | Create Spring Boot Java Project Skeleton | None |
|
||||
| [create-spring-boot-kotlin-project](../skills/create-spring-boot-kotlin-project/SKILL.md) | Create Spring Boot Kotlin Project Skeleton | None |
|
||||
| [create-technical-spike](../skills/create-technical-spike/SKILL.md) | Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation. | None |
|
||||
| [create-tldr-page](../skills/create-tldr-page/SKILL.md) | Create a tldr page from documentation URLs and command examples, requiring both URL and command name. | None |
|
||||
| [create-web-form](../skills/create-web-form/SKILL.md) | Create robust, accessible web forms with best practices for HTML structure, CSS styling, JavaScript interactivity, form validation, and server-side processing. Use when asked to "create a form", "build a web form", "add a contact form", "make a signup form", or when building any HTML form with data handling. Covers PHP and Python backends, MySQL database integration, REST APIs, XML data exchange, accessibility (ARIA), and progressive web apps. | `references/accessibility.md`<br />`references/aria-form-role.md`<br />`references/css-styling.md`<br />`references/form-basics.md`<br />`references/form-controls.md`<br />`references/form-data-handling.md`<br />`references/html-form-elements.md`<br />`references/html-form-example.md`<br />`references/hypertext-transfer-protocol.md`<br />`references/javascript.md`<br />`references/php-cookies.md`<br />`references/php-forms.md`<br />`references/php-json.md`<br />`references/php-mysql-database.md`<br />`references/progressive-web-app.md`<br />`references/python-as-web-framework.md`<br />`references/python-contact-form.md`<br />`references/python-flask-app.md`<br />`references/python-flask.md`<br />`references/security.md`<br />`references/styling-web-forms.md`<br />`references/web-api.md`<br />`references/web-performance.md`<br />`references/xml.md` |
|
||||
| [csharp-async](../skills/csharp-async/SKILL.md) | Get best practices for C# async programming | None |
|
||||
| [csharp-docs](../skills/csharp-docs/SKILL.md) | Ensure that C# types are documented with XML comments and follow best practices for documentation. | None |
|
||||
| [csharp-mcp-server-generator](../skills/csharp-mcp-server-generator/SKILL.md) | Generate a complete MCP server project in C# with tools, prompts, and proper configuration | None |
|
||||
| [csharp-mstest](../skills/csharp-mstest/SKILL.md) | Get best practices for MSTest 3.x/4.x unit testing, including modern assertion APIs and data-driven tests | None |
|
||||
| [csharp-nunit](../skills/csharp-nunit/SKILL.md) | Get best practices for NUnit unit testing, including data-driven tests | None |
|
||||
| [csharp-tunit](../skills/csharp-tunit/SKILL.md) | Get best practices for TUnit unit testing, including data-driven tests | None |
|
||||
| [csharp-xunit](../skills/csharp-xunit/SKILL.md) | Get best practices for XUnit unit testing, including data-driven tests | None |
|
||||
| [dataverse-python-advanced-patterns](../skills/dataverse-python-advanced-patterns/SKILL.md) | Generate production code for Dataverse SDK using advanced patterns, error handling, and optimization techniques. | None |
|
||||
| [dataverse-python-production-code](../skills/dataverse-python-production-code/SKILL.md) | Generate production-ready Python code using Dataverse SDK with error handling, optimization, and best practices | None |
|
||||
| [dataverse-python-quickstart](../skills/dataverse-python-quickstart/SKILL.md) | Generate Python SDK setup + CRUD + bulk + paging snippets using official patterns. | None |
|
||||
| [dataverse-python-usecase-builder](../skills/dataverse-python-usecase-builder/SKILL.md) | Generate complete solutions for specific Dataverse SDK use cases with architecture recommendations | None |
|
||||
| [debian-linux-triage](../skills/debian-linux-triage/SKILL.md) | Triage and resolve Debian Linux issues with apt, systemd, and AppArmor-aware guidance. | None |
|
||||
| [declarative-agents](../skills/declarative-agents/SKILL.md) | Complete development kit for Microsoft 365 Copilot declarative agents with three comprehensive workflows (basic, advanced, validation), TypeSpec support, and Microsoft 365 Agents Toolkit integration | None |
|
||||
| [devops-rollout-plan](../skills/devops-rollout-plan/SKILL.md) | Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes | None |
|
||||
| [documentation-writer](../skills/documentation-writer/SKILL.md) | 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. | None |
|
||||
| [dotnet-best-practices](../skills/dotnet-best-practices/SKILL.md) | Ensure .NET/C# code meets best practices for the solution/project. | None |
|
||||
| [dotnet-design-pattern-review](../skills/dotnet-design-pattern-review/SKILL.md) | Review the C#/.NET code for design pattern implementation and suggest improvements. | None |
|
||||
| [dotnet-upgrade](../skills/dotnet-upgrade/SKILL.md) | Ready-to-use prompts for comprehensive .NET framework upgrade analysis and execution | None |
|
||||
| [editorconfig](../skills/editorconfig/SKILL.md) | Generates a comprehensive and best-practice-oriented .editorconfig file based on project analysis and user preferences. | None |
|
||||
| [ef-core](../skills/ef-core/SKILL.md) | Get best practices for Entity Framework Core | None |
|
||||
| [entra-agent-user](../skills/entra-agent-user/SKILL.md) | Create Agent Users in Microsoft Entra ID from Agent Identities, enabling AI agents to act as digital workers with user identity capabilities in Microsoft 365 and Azure environments. | None |
|
||||
| [excalidraw-diagram-generator](../skills/excalidraw-diagram-generator/SKILL.md) | Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw. | `references/element-types.md`<br />`references/excalidraw-schema.md`<br />`scripts/.gitignore`<br />`scripts/README.md`<br />`scripts/add-arrow.py`<br />`scripts/add-icon-to-diagram.py`<br />`scripts/split-excalidraw-library.py`<br />`templates/business-flow-swimlane-template.excalidraw`<br />`templates/class-diagram-template.excalidraw`<br />`templates/data-flow-diagram-template.excalidraw`<br />`templates/er-diagram-template.excalidraw`<br />`templates/flowchart-template.excalidraw`<br />`templates/mindmap-template.excalidraw`<br />`templates/relationship-template.excalidraw`<br />`templates/sequence-diagram-template.excalidraw` |
|
||||
| [fabric-lakehouse](../skills/fabric-lakehouse/SKILL.md) | Use this skill to get context about Fabric Lakehouse and its features for software systems and AI-powered functions. It offers descriptions of Lakehouse data components, organization with schemas and shortcuts, access control, and code examples. This skill supports users in designing, building, and optimizing Lakehouse solutions using best practices. | `references/getdata.md`<br />`references/pyspark.md` |
|
||||
| [fedora-linux-triage](../skills/fedora-linux-triage/SKILL.md) | Triage and resolve Fedora issues with dnf, systemd, and SELinux-aware guidance. | None |
|
||||
| [finalize-agent-prompt](../skills/finalize-agent-prompt/SKILL.md) | Finalize prompt file using the role of an AI agent to polish the prompt for the end user. | None |
|
||||
| [finnish-humanizer](../skills/finnish-humanizer/SKILL.md) | Detect and remove AI-generated markers from Finnish text, making it sound like a native Finnish speaker wrote it. Use when asked to "humanize", "naturalize", or "remove AI feel" from Finnish text, or when editing .md/.txt files containing Finnish content. Identifies 26 patterns (12 Finnish-specific + 14 universal) and 4 style markers. | `references/patterns.md` |
|
||||
| [first-ask](../skills/first-ask/SKILL.md) | Interactive, input-tool powered, task refinement workflow: interrogates scope, deliverables, constraints before carrying out the task; Requires the Joyride extension. | None |
|
||||
| [fluentui-blazor](../skills/fluentui-blazor/SKILL.md) | Guide for using the Microsoft Fluent UI Blazor component library (Microsoft.FluentUI.AspNetCore.Components NuGet package) in Blazor applications. Use this when the user is building a Blazor app with Fluent UI components, setting up the library, using FluentUI components like FluentButton, FluentDataGrid, FluentDialog, FluentToast, FluentNavMenu, FluentTextField, FluentSelect, FluentAutocomplete, FluentDesignTheme, or any component prefixed with "Fluent". Also use when troubleshooting missing providers, JS interop issues, or theming. | `references/DATAGRID.md`<br />`references/LAYOUT-AND-NAVIGATION.md`<br />`references/SETUP.md`<br />`references/THEMING.md` |
|
||||
| [folder-structure-blueprint-generator](../skills/folder-structure-blueprint-generator/SKILL.md) | Comprehensive technology-agnostic prompt for analyzing and documenting project folder structures. Auto-detects project types (.NET, Java, React, Angular, Python, Node.js, Flutter), generates detailed blueprints with visualization options, naming conventions, file placement patterns, and extension templates for maintaining consistent code organization across diverse technology stacks. | None |
|
||||
| [game-engine](../skills/game-engine/SKILL.md) | Expert skill for building web-based game engines and games using HTML5, Canvas, WebGL, and JavaScript. Use when asked to create games, build game engines, implement game physics, handle collision detection, set up game loops, manage sprites, add game controls, or work with 2D/3D rendering. Covers techniques for platformers, breakout-style games, maze games, tilemaps, audio, multiplayer via WebRTC, and publishing games. | `assets/2d-maze-game.md`<br />`assets/2d-platform-game.md`<br />`assets/gameBase-template-repo.md`<br />`assets/paddle-game-template.md`<br />`assets/simple-2d-engine.md`<br />`references/3d-web-games.md`<br />`references/algorithms.md`<br />`references/basics.md`<br />`references/game-control-mechanisms.md`<br />`references/game-engine-core-principles.md`<br />`references/game-publishing.md`<br />`references/techniques.md`<br />`references/terminology.md`<br />`references/web-apis.md` |
|
||||
| [gen-specs-as-issues](../skills/gen-specs-as-issues/SKILL.md) | This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation. | None |
|
||||
| [generate-custom-instructions-from-codebase](../skills/generate-custom-instructions-from-codebase/SKILL.md) | Migration and code evolution instructions generator for GitHub Copilot. Analyzes differences between two project versions (branches, commits, or releases) to create precise instructions allowing Copilot to maintain consistency during technology migrations, major refactoring, or framework version upgrades. | None |
|
||||
| [gh-cli](../skills/gh-cli/SKILL.md) | GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line. | None |
|
||||
| [git-commit](../skills/git-commit/SKILL.md) | Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping | None |
|
||||
| [git-flow-branch-creator](../skills/git-flow-branch-creator/SKILL.md) | Intelligent Git Flow branch creator that analyzes git status/diff and creates appropriate branches following the nvie Git Flow branching model. | None |
|
||||
| [github-copilot-starter](../skills/github-copilot-starter/SKILL.md) | Set up complete GitHub Copilot configuration for a new project based on technology stack | None |
|
||||
| [github-issues](../skills/github-issues/SKILL.md) | Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or manage issue workflows. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", or any GitHub issue management task. | `references/templates.md` |
|
||||
| [go-mcp-server-generator](../skills/go-mcp-server-generator/SKILL.md) | Generate a complete Go MCP server project with proper structure, dependencies, and implementation using the official github.com/modelcontextprotocol/go-sdk. | None |
|
||||
| [image-manipulation-image-magick](../skills/image-manipulation-image-magick/SKILL.md) | Process and manipulate images using ImageMagick. Supports resizing, format conversion, batch processing, and retrieving image metadata. Use when working with images, creating thumbnails, resizing wallpapers, or performing batch image operations. | None |
|
||||
| [java-add-graalvm-native-image-support](../skills/java-add-graalvm-native-image-support/SKILL.md) | GraalVM Native Image expert that adds native image support to Java applications, builds the project, analyzes build errors, applies fixes, and iterates until successful compilation using Oracle best practices. | None |
|
||||
| [java-docs](../skills/java-docs/SKILL.md) | Ensure that Java types are documented with Javadoc comments and follow best practices for documentation. | None |
|
||||
| [java-junit](../skills/java-junit/SKILL.md) | Get best practices for JUnit 5 unit testing, including data-driven tests | None |
|
||||
| [java-mcp-server-generator](../skills/java-mcp-server-generator/SKILL.md) | Generate a complete Model Context Protocol server project in Java using the official MCP Java SDK with reactive streams and optional Spring Boot integration. | None |
|
||||
| [java-refactoring-extract-method](../skills/java-refactoring-extract-method/SKILL.md) | Refactoring using Extract Methods in Java Language | None |
|
||||
| [java-refactoring-remove-parameter](../skills/java-refactoring-remove-parameter/SKILL.md) | Refactoring using Remove Parameter in Java Language | None |
|
||||
| [java-springboot](../skills/java-springboot/SKILL.md) | Get best practices for developing applications with Spring Boot. | None |
|
||||
| [javascript-typescript-jest](../skills/javascript-typescript-jest/SKILL.md) | Best practices for writing JavaScript/TypeScript tests using Jest, including mocking strategies, test structure, and common patterns. | None |
|
||||
| [kotlin-mcp-server-generator](../skills/kotlin-mcp-server-generator/SKILL.md) | Generate a complete Kotlin MCP server project with proper structure, dependencies, and implementation using the official io.modelcontextprotocol:kotlin-sdk library. | None |
|
||||
| [kotlin-springboot](../skills/kotlin-springboot/SKILL.md) | Get best practices for developing applications with Spring Boot and Kotlin. | None |
|
||||
| [legacy-circuit-mockups](../skills/legacy-circuit-mockups/SKILL.md) | Generate breadboard circuit mockups and visual diagrams using HTML5 Canvas drawing techniques. Use when asked to create circuit layouts, visualize electronic component placements, draw breadboard diagrams, mockup 6502 builds, generate retro computer schematics, or design vintage electronics projects. Supports 555 timers, W65C02S microprocessors, 28C256 EEPROMs, W65C22 VIA chips, 7400-series logic gates, LEDs, resistors, capacitors, switches, buttons, crystals, and wires. | `references/28256-eeprom.md`<br />`references/555.md`<br />`references/6502.md`<br />`references/6522.md`<br />`references/6C62256.md`<br />`references/7400-series.md`<br />`references/assembly-compiler.md`<br />`references/assembly-language.md`<br />`references/basic-electronic-components.md`<br />`references/breadboard.md`<br />`references/common-breadboard-components.md`<br />`references/connecting-electronic-components.md`<br />`references/emulator-28256-eeprom.md`<br />`references/emulator-6502.md`<br />`references/emulator-6522.md`<br />`references/emulator-6C62256.md`<br />`references/emulator-lcd.md`<br />`references/lcd.md`<br />`references/minipro.md`<br />`references/t48eeprom-programmer.md` |
|
||||
| [make-repo-contribution](../skills/make-repo-contribution/SKILL.md) | All changes to code must follow the guidance documented in the repository. Before any issue is filed, branch is made, commits generated, or pull request (or PR) created, a search must be done to ensure the right steps are followed. Whenever asked to create an issue, commit messages, to push code, or create a PR, use this skill so everything is done correctly. | `assets/issue-template.md`<br />`assets/pr-template.md` |
|
||||
| [make-skill-template](../skills/make-skill-template/SKILL.md) | Create new Agent Skills for GitHub Copilot from prompts or by duplicating this template. Use when asked to "create a skill", "make a new skill", "scaffold a skill", or when building specialized AI capabilities with bundled resources. Generates SKILL.md files with proper frontmatter, directory structure, and optional scripts/references/assets folders. | None |
|
||||
| [markdown-to-html](../skills/markdown-to-html/SKILL.md) | Convert Markdown files to HTML similar to `marked.js`, `pandoc`, `gomarkdown/markdown`, or similar tools; or writing custom script to convert markdown to html and/or working on web template systems like `jekyll/jekyll`, `gohugoio/hugo`, or similar web templating systems that utilize markdown documents, converting them to html. Use when asked to "convert markdown to html", "transform md to html", "render markdown", "generate html from markdown", or when working with .md files and/or web a templating system that converts markdown to HTML output. Supports CLI and Node.js workflows with GFM, CommonMark, and standard Markdown flavors. | `references/basic-markdown-to-html.md`<br />`references/basic-markdown.md`<br />`references/code-blocks-to-html.md`<br />`references/code-blocks.md`<br />`references/collapsed-sections-to-html.md`<br />`references/collapsed-sections.md`<br />`references/gomarkdown.md`<br />`references/hugo.md`<br />`references/jekyll.md`<br />`references/marked.md`<br />`references/pandoc.md`<br />`references/tables-to-html.md`<br />`references/tables.md`<br />`references/writing-mathematical-expressions-to-html.md`<br />`references/writing-mathematical-expressions.md` |
|
||||
| [mcp-cli](../skills/mcp-cli/SKILL.md) | Interface for MCP (Model Context Protocol) servers via CLI. Use when you need to interact with external tools, APIs, or data sources through MCP servers, list available MCP servers/tools, or call MCP tools from command line. | None |
|
||||
| [mcp-configure](../skills/mcp-configure/SKILL.md) | Configure an MCP server for GitHub Copilot with your Dataverse environment. | None |
|
||||
| [mcp-copilot-studio-server-generator](../skills/mcp-copilot-studio-server-generator/SKILL.md) | Generate a complete MCP server implementation optimized for Copilot Studio integration with proper schema constraints and streamable HTTP support | None |
|
||||
| [mcp-create-adaptive-cards](../skills/mcp-create-adaptive-cards/SKILL.md) | Skill converted from mcp-create-adaptive-cards.prompt.md | None |
|
||||
| [mcp-create-declarative-agent](../skills/mcp-create-declarative-agent/SKILL.md) | Skill converted from mcp-create-declarative-agent.prompt.md | None |
|
||||
| [mcp-deploy-manage-agents](../skills/mcp-deploy-manage-agents/SKILL.md) | Skill converted from mcp-deploy-manage-agents.prompt.md | None |
|
||||
| [meeting-minutes](../skills/meeting-minutes/SKILL.md) | Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps. | None |
|
||||
| [memory-merger](../skills/memory-merger/SKILL.md) | Merges mature lessons from a domain memory file into its instruction file. Syntax: `/memory-merger >domain [scope]` where scope is `global` (default), `user`, `workspace`, or `ws`. | None |
|
||||
| [microsoft-code-reference](../skills/microsoft-code-reference/SKILL.md) | Look up Microsoft API references, find working code samples, and verify SDK code is correct. Use when working with Azure SDKs, .NET libraries, or Microsoft APIs—to find the right method, check parameters, get working examples, or troubleshoot errors. Catches hallucinated methods, wrong signatures, and deprecated patterns by querying official docs. | None |
|
||||
| [microsoft-docs](../skills/microsoft-docs/SKILL.md) | Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more. Uses Microsoft Learn MCP as the default, with Context7 and Aspire MCP for content that lives outside learn.microsoft.com. | None |
|
||||
| [microsoft-skill-creator](../skills/microsoft-skill-creator/SKILL.md) | Create agent skills for Microsoft technologies using Learn MCP tools. Use when users want to create a skill that teaches agents about any Microsoft technology, library, framework, or service (Azure, .NET, M365, VS Code, Bicep, etc.). Investigates topics deeply, then generates a hybrid skill storing essential knowledge locally while enabling dynamic deeper investigation. | `references/skill-templates.md` |
|
||||
| [mkdocs-translations](../skills/mkdocs-translations/SKILL.md) | Generate a language translation for a mkdocs documentation stack. | None |
|
||||
| [model-recommendation](../skills/model-recommendation/SKILL.md) | Analyze chatmode or prompt files and recommend optimal AI models based on task complexity, required capabilities, and cost-efficiency | None |
|
||||
| [multi-stage-dockerfile](../skills/multi-stage-dockerfile/SKILL.md) | Create optimized multi-stage Dockerfiles for any language or framework | None |
|
||||
| [my-issues](../skills/my-issues/SKILL.md) | List my issues in the current repository | None |
|
||||
| [my-pull-requests](../skills/my-pull-requests/SKILL.md) | List my pull requests in the current repository | None |
|
||||
| [nano-banana-pro-openrouter](../skills/nano-banana-pro-openrouter/SKILL.md) | Generate or edit images via OpenRouter with the Gemini 3 Pro Image model. Use for prompt-only image generation, image edits, and multi-image compositing; supports 1K/2K/4K output. | `assets/SYSTEM_TEMPLATE`<br />`scripts/generate_image.py` |
|
||||
| [next-intl-add-language](../skills/next-intl-add-language/SKILL.md) | Add new language to a Next.js + next-intl application | None |
|
||||
| [nuget-manager](../skills/nuget-manager/SKILL.md) | Manage NuGet packages in .NET projects/solutions. Use this skill when adding, removing, or updating NuGet package versions. It enforces using `dotnet` CLI for package management and provides strict procedures for direct file edits only when updating versions. | None |
|
||||
| [openapi-to-application-code](../skills/openapi-to-application-code/SKILL.md) | Generate a complete, production-ready application from an OpenAPI specification | None |
|
||||
| [pdftk-server](../skills/pdftk-server/SKILL.md) | Skill for using the command-line tool pdftk (PDFtk Server) for working with PDF files. Use when asked to merge PDFs, split PDFs, rotate pages, encrypt or decrypt PDFs, fill PDF forms, apply watermarks, stamp overlays, extract metadata, burst documents into pages, repair corrupted PDFs, attach or extract files, or perform any PDF manipulation from the command line. | `references/download.md`<br />`references/pdftk-cli-examples.md`<br />`references/pdftk-man-page.md`<br />`references/pdftk-server-license.md`<br />`references/third-party-materials.md` |
|
||||
| [penpot-uiux-design](../skills/penpot-uiux-design/SKILL.md) | Comprehensive guide for creating professional UI/UX designs in Penpot using MCP tools. Use this skill when: (1) Creating new UI/UX designs for web, mobile, or desktop applications, (2) Building design systems with components and tokens, (3) Designing dashboards, forms, navigation, or landing pages, (4) Applying accessibility standards and best practices, (5) Following platform guidelines (iOS, Android, Material Design), (6) Reviewing or improving existing Penpot designs for usability. Triggers: "design a UI", "create interface", "build layout", "design dashboard", "create form", "design landing page", "make it accessible", "design system", "component library". | `references/accessibility.md`<br />`references/component-patterns.md`<br />`references/platform-guidelines.md`<br />`references/setup-troubleshooting.md` |
|
||||
| [php-mcp-server-generator](../skills/php-mcp-server-generator/SKILL.md) | Generate a complete PHP Model Context Protocol server project with tools, resources, prompts, and tests using the official PHP SDK | None |
|
||||
| [plantuml-ascii](../skills/plantuml-ascii/SKILL.md) | Generate ASCII art diagrams using PlantUML text mode. Use when user asks to create ASCII diagrams, text-based diagrams, terminal-friendly diagrams, or mentions plantuml ascii, text diagram, ascii art diagram. Supports: Converting PlantUML diagrams to ASCII art, Creating sequence diagrams, class diagrams, flowcharts in ASCII format, Generating Unicode-enhanced ASCII art with -utxt flag | None |
|
||||
| [playwright-automation-fill-in-form](../skills/playwright-automation-fill-in-form/SKILL.md) | Automate filling in a form using Playwright MCP | None |
|
||||
| [playwright-explore-website](../skills/playwright-explore-website/SKILL.md) | Website exploration for testing using Playwright MCP | None |
|
||||
| [playwright-generate-test](../skills/playwright-generate-test/SKILL.md) | Generate a Playwright test based on a scenario using Playwright MCP | None |
|
||||
| [polyglot-test-agent](../skills/polyglot-test-agent/SKILL.md) | Generates comprehensive, workable unit tests for any programming language using a multi-agent pipeline. Use when asked to generate tests, write unit tests, improve test coverage, add test coverage, create test files, or test a codebase. Supports C#, TypeScript, JavaScript, Python, Go, Rust, Java, and more. Orchestrates research, planning, and implementation phases to produce tests that compile, pass, and follow project conventions. | `unit-test-generation.prompt.md` |
|
||||
| [postgresql-code-review](../skills/postgresql-code-review/SKILL.md) | PostgreSQL-specific code review assistant focusing on PostgreSQL best practices, anti-patterns, and unique quality standards. Covers JSONB operations, array usage, custom types, schema design, function optimization, and PostgreSQL-exclusive security features like Row Level Security (RLS). | None |
|
||||
| [postgresql-optimization](../skills/postgresql-optimization/SKILL.md) | PostgreSQL-specific development assistant focusing on unique PostgreSQL features, advanced data types, and PostgreSQL-exclusive capabilities. Covers JSONB operations, array types, custom types, range/geometric types, full-text search, window functions, and PostgreSQL extensions ecosystem. | None |
|
||||
| [power-apps-code-app-scaffold](../skills/power-apps-code-app-scaffold/SKILL.md) | Scaffold a complete Power Apps Code App project with PAC CLI setup, SDK integration, and connector configuration | None |
|
||||
| [power-bi-dax-optimization](../skills/power-bi-dax-optimization/SKILL.md) | Comprehensive Power BI DAX formula optimization prompt for improving performance, readability, and maintainability of DAX calculations. | None |
|
||||
| [power-bi-model-design-review](../skills/power-bi-model-design-review/SKILL.md) | Comprehensive Power BI data model design review prompt for evaluating model architecture, relationships, and optimization opportunities. | None |
|
||||
| [power-bi-performance-troubleshooting](../skills/power-bi-performance-troubleshooting/SKILL.md) | Systematic Power BI performance troubleshooting prompt for identifying, diagnosing, and resolving performance issues in Power BI models, reports, and queries. | None |
|
||||
| [power-bi-report-design-consultation](../skills/power-bi-report-design-consultation/SKILL.md) | Power BI report visualization design prompt for creating effective, user-friendly, and accessible reports with optimal chart selection and layout design. | None |
|
||||
| [power-platform-mcp-connector-suite](../skills/power-platform-mcp-connector-suite/SKILL.md) | Generate complete Power Platform custom connector with MCP integration for Copilot Studio - includes schema generation, troubleshooting, and validation | None |
|
||||
| [powerbi-modeling](../skills/powerbi-modeling/SKILL.md) | Power BI semantic modeling assistant for building optimized data models. Use when working with Power BI semantic models, creating measures, designing star schemas, configuring relationships, implementing RLS, or optimizing model performance. Triggers on queries about DAX calculations, table relationships, dimension/fact table design, naming conventions, model documentation, cardinality, cross-filter direction, calculation groups, and data model best practices. Always connects to the active model first using power-bi-modeling MCP tools to understand the data structure before providing guidance. | `references/MEASURES-DAX.md`<br />`references/PERFORMANCE.md`<br />`references/RELATIONSHIPS.md`<br />`references/RLS.md`<br />`references/STAR-SCHEMA.md` |
|
||||
| [prd](../skills/prd/SKILL.md) | Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis. | None |
|
||||
| [project-workflow-analysis-blueprint-generator](../skills/project-workflow-analysis-blueprint-generator/SKILL.md) | Comprehensive technology-agnostic prompt generator for documenting end-to-end application workflows. Automatically detects project architecture patterns, technology stacks, and data flow patterns to generate detailed implementation blueprints covering entry points, service layers, data access, error handling, and testing approaches across multiple technologies including .NET, Java/Spring, React, and microservices architectures. | None |
|
||||
| [prompt-builder](../skills/prompt-builder/SKILL.md) | Guide users through creating high-quality GitHub Copilot prompts with proper structure, tools, and best practices. | None |
|
||||
| [pytest-coverage](../skills/pytest-coverage/SKILL.md) | Run pytest tests with coverage, discover lines missing coverage, and increase coverage to 100%. | None |
|
||||
| [python-mcp-server-generator](../skills/python-mcp-server-generator/SKILL.md) | Generate a complete MCP server project in Python with tools, resources, and proper configuration | None |
|
||||
| [quasi-coder](../skills/quasi-coder/SKILL.md) | Expert 10x engineer skill for interpreting and implementing code from shorthand, quasi-code, and natural language descriptions. Use when collaborators provide incomplete code snippets, pseudo-code, or descriptions with potential typos or incorrect terminology. Excels at translating non-technical or semi-technical descriptions into production-quality code. | None |
|
||||
| [readme-blueprint-generator](../skills/readme-blueprint-generator/SKILL.md) | Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans .github/copilot directory files and copilot-instructions.md to extract project information, technology stack, architecture, development workflow, coding standards, and testing approaches while generating well-structured markdown documentation with proper formatting, cross-references, and developer-focused content. | None |
|
||||
| [refactor](../skills/refactor/SKILL.md) | Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements. | None |
|
||||
| [refactor-method-complexity-reduce](../skills/refactor-method-complexity-reduce/SKILL.md) | Refactor given method `${input:methodName}` to reduce its cognitive complexity to `${input:complexityThreshold}` or below, by extracting helper methods. | None |
|
||||
| [refactor-plan](../skills/refactor-plan/SKILL.md) | Plan a multi-file refactor with proper sequencing and rollback steps | None |
|
||||
| [remember](../skills/remember/SKILL.md) | Transforms lessons learned into domain-organized memory instructions (global or workspace). Syntax: `/remember [>domain [scope]] lesson clue` where scope is `global` (default), `user`, `workspace`, or `ws`. | None |
|
||||
| [remember-interactive-programming](../skills/remember-interactive-programming/SKILL.md) | A micro-prompt that reminds the agent that it is an interactive programmer. Works great in Clojure when Copilot has access to the REPL (probably via Backseat Driver). Will work with any system that has a live REPL that the agent can use. Adapt the prompt with any specific reminders in your workflow and/or workspace. | None |
|
||||
| [repo-story-time](../skills/repo-story-time/SKILL.md) | Generate a comprehensive repository summary and narrative story from commit history | None |
|
||||
| [review-and-refactor](../skills/review-and-refactor/SKILL.md) | Review and refactor code in your project according to defined instructions | None |
|
||||
| [ruby-mcp-server-generator](../skills/ruby-mcp-server-generator/SKILL.md) | Generate a complete Model Context Protocol server project in Ruby using the official MCP Ruby SDK gem. | None |
|
||||
| [rust-mcp-server-generator](../skills/rust-mcp-server-generator/SKILL.md) | Generate a complete Rust Model Context Protocol server project with tools, prompts, resources, and tests using the official rmcp SDK | None |
|
||||
| [scoutqa-test](../skills/scoutqa-test/SKILL.md) | This skill should be used when the user asks to "test this website", "run exploratory testing", "check for accessibility issues", "verify the login flow works", "find bugs on this page", or requests automated QA testing. Triggers on web application testing scenarios including smoke tests, accessibility audits, e-commerce flows, and user flow validation using ScoutQA CLI. IMPORTANT: Use this skill proactively after implementing web application features to verify they work correctly - don't wait for the user to ask for testing. | None |
|
||||
| [shuffle-json-data](../skills/shuffle-json-data/SKILL.md) | Shuffle repetitive JSON objects safely by validating schema consistency before randomising entries. | None |
|
||||
| [snowflake-semanticview](../skills/snowflake-semanticview/SKILL.md) | Create, alter, and validate Snowflake semantic views using Snowflake CLI (snow). Use when asked to build or troubleshoot semantic views/semantic layer definitions with CREATE/ALTER SEMANTIC VIEW, to validate semantic-view DDL against Snowflake via CLI, or to guide Snowflake CLI installation and connection setup. | None |
|
||||
| [sponsor-finder](../skills/sponsor-finder/SKILL.md) | Find which of a GitHub repository's dependencies are sponsorable via GitHub Sponsors. Uses deps.dev API for dependency resolution across npm, PyPI, Cargo, Go, RubyGems, Maven, and NuGet. Checks npm funding metadata, FUNDING.yml files, and web search. Verifies every link. Shows direct and transitive dependencies with OSSF Scorecard health data. Invoke with /sponsor followed by a GitHub owner/repo (e.g. "/sponsor expressjs/express"). | None |
|
||||
| [sql-code-review](../skills/sql-code-review/SKILL.md) | Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Focuses on SQL injection prevention, access control, code standards, and anti-pattern detection. Complements SQL optimization prompt for complete development coverage. | None |
|
||||
| [sql-optimization](../skills/sql-optimization/SKILL.md) | Universal SQL performance optimization assistant for comprehensive query tuning, indexing strategies, and database performance analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Provides execution plan analysis, pagination optimization, batch operations, and performance monitoring guidance. | None |
|
||||
| [structured-autonomy-generate](../skills/structured-autonomy-generate/SKILL.md) | Structured Autonomy Implementation Generator Prompt | None |
|
||||
| [structured-autonomy-implement](../skills/structured-autonomy-implement/SKILL.md) | Structured Autonomy Implementation Prompt | None |
|
||||
| [structured-autonomy-plan](../skills/structured-autonomy-plan/SKILL.md) | Structured Autonomy Planning Prompt | None |
|
||||
| [suggest-awesome-github-copilot-agents](../skills/suggest-awesome-github-copilot-agents/SKILL.md) | 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, and identifying outdated agents that need updates. | None |
|
||||
| [suggest-awesome-github-copilot-instructions](../skills/suggest-awesome-github-copilot-instructions/SKILL.md) | 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, and identifying outdated instructions that need updates. | None |
|
||||
| [suggest-awesome-github-copilot-prompts](../skills/suggest-awesome-github-copilot-prompts/SKILL.md) | 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, and identifying outdated prompts that need updates. | None |
|
||||
| [suggest-awesome-github-copilot-skills](../skills/suggest-awesome-github-copilot-skills/SKILL.md) | Suggest relevant GitHub Copilot skills from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing skills in this repository, and identifying outdated skills that need updates. | None |
|
||||
| [swift-mcp-server-generator](../skills/swift-mcp-server-generator/SKILL.md) | Generate a complete Model Context Protocol server project in Swift using the official MCP Swift SDK package. | None |
|
||||
| [technology-stack-blueprint-generator](../skills/technology-stack-blueprint-generator/SKILL.md) | Comprehensive technology stack blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks, programming languages, and implementation patterns across multiple platforms (.NET, Java, JavaScript, React, Python). Generates configurable blueprints with version information, licensing details, usage patterns, coding conventions, and visual diagrams. Provides implementation-ready templates and maintains architectural consistency for guided development. | None |
|
||||
| [terraform-azurerm-set-diff-analyzer](../skills/terraform-azurerm-set-diff-analyzer/SKILL.md) | Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes. | `references/azurerm_set_attributes.json`<br />`references/azurerm_set_attributes.md`<br />`scripts/.gitignore`<br />`scripts/README.md`<br />`scripts/analyze_plan.py` |
|
||||
| [tldr-prompt](../skills/tldr-prompt/SKILL.md) | Create tldr summaries for GitHub Copilot files (prompts, agents, instructions, collections), MCP servers, or documentation from URLs and queries. | None |
|
||||
| [transloadit-media-processing](../skills/transloadit-media-processing/SKILL.md) | Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS/MP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale. | None |
|
||||
| [typescript-mcp-server-generator](../skills/typescript-mcp-server-generator/SKILL.md) | Generate a complete MCP server project in TypeScript with tools, resources, and proper configuration | None |
|
||||
| [typespec-api-operations](../skills/typespec-api-operations/SKILL.md) | Add GET, POST, PATCH, and DELETE operations to a TypeSpec API plugin with proper routing, parameters, and adaptive cards | None |
|
||||
| [typespec-create-agent](../skills/typespec-create-agent/SKILL.md) | Generate a complete TypeSpec declarative agent with instructions, capabilities, and conversation starters for Microsoft 365 Copilot | None |
|
||||
| [typespec-create-api-plugin](../skills/typespec-create-api-plugin/SKILL.md) | Generate a TypeSpec API plugin with REST operations, authentication, and Adaptive Cards for Microsoft 365 Copilot | None |
|
||||
| [update-avm-modules-in-bicep](../skills/update-avm-modules-in-bicep/SKILL.md) | Update Azure Verified Modules (AVM) to latest versions in Bicep files. | None |
|
||||
| [update-implementation-plan](../skills/update-implementation-plan/SKILL.md) | 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. | None |
|
||||
| [update-llms](../skills/update-llms/SKILL.md) | 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/ | None |
|
||||
| [update-markdown-file-index](../skills/update-markdown-file-index/SKILL.md) | Update a markdown file section with an index/table of files from a specified folder. | None |
|
||||
| [update-oo-component-documentation](../skills/update-oo-component-documentation/SKILL.md) | Update existing object-oriented component documentation following industry best practices and architectural documentation standards. | None |
|
||||
| [update-specification](../skills/update-specification/SKILL.md) | Update an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code. | None |
|
||||
| [vscode-ext-commands](../skills/vscode-ext-commands/SKILL.md) | Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and good practices | None |
|
||||
| [vscode-ext-localization](../skills/vscode-ext-localization/SKILL.md) | Guidelines for proper localization of VS Code extensions, following VS Code extension development guidelines, libraries and good practices | None |
|
||||
| [web-design-reviewer](../skills/web-design-reviewer/SKILL.md) | This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level. | `references/framework-fixes.md`<br />`references/visual-checklist.md` |
|
||||
| [webapp-testing](../skills/webapp-testing/SKILL.md) | Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs. | `test-helper.js` |
|
||||
| [what-context-needed](../skills/what-context-needed/SKILL.md) | Ask Copilot what files it needs to see before answering a question | None |
|
||||
| [winapp-cli](../skills/winapp-cli/SKILL.md) | Windows App Development CLI (winapp) for building, packaging, and deploying Windows applications. Use when asked to initialize Windows app projects, create MSIX packages, generate AppxManifest.xml, manage development certificates, add package identity for debugging, sign packages, or access Windows SDK build tools. Supports .NET, C++, Electron, Rust, Tauri, and cross-platform frameworks targeting Windows. | None |
|
||||
| [workiq-copilot](../skills/workiq-copilot/SKILL.md) | Guides the Copilot CLI on how to use the WorkIQ CLI/MCP server to query Microsoft 365 Copilot data (emails, meetings, docs, Teams, people) for live context, summaries, and recommendations. | None |
|
||||
| [write-coding-standards-from-file](../skills/write-coding-standards-from-file/SKILL.md) | 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. | None |
|
||||
|
||||
40
docs/README.workflows.md
Normal file
40
docs/README.workflows.md
Normal file
@@ -0,0 +1,40 @@
|
||||
# ⚡ Agentic Workflows
|
||||
|
||||
[Agentic Workflows](https://github.github.com/gh-aw) are AI-powered repository automations that run coding agents in GitHub Actions. Defined in markdown with natural language instructions, they enable event-triggered and scheduled automation with built-in guardrails and security-first design.
|
||||
### How to Contribute
|
||||
|
||||
See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-agentic-workflows) for guidelines on how to contribute new workflows, improve existing ones, and share your use cases.
|
||||
|
||||
### How to Use Agentic Workflows
|
||||
|
||||
**What's Included:**
|
||||
- Each workflow is a single `.md` file with YAML frontmatter and natural language instructions
|
||||
- Workflows are compiled to `.lock.yml` GitHub Actions files via `gh aw compile`
|
||||
- Workflows follow the [GitHub Agentic Workflows specification](https://github.github.com/gh-aw)
|
||||
|
||||
**To Install:**
|
||||
- Install the `gh aw` CLI extension: `gh extension install github/gh-aw`
|
||||
- Copy the workflow `.md` file to your repository's `.github/workflows/` directory
|
||||
- Compile with `gh aw compile` to generate the `.lock.yml` file
|
||||
- Commit both the `.md` and `.lock.yml` files
|
||||
|
||||
**To Activate/Use:**
|
||||
- Workflows run automatically based on their configured triggers (schedules, events, slash commands)
|
||||
- Use `gh aw run <workflow>` to trigger a manual run
|
||||
- Monitor runs with `gh aw status` and `gh aw logs`
|
||||
|
||||
**When to Use:**
|
||||
- Automate issue triage and labeling
|
||||
- Generate daily status reports
|
||||
- Maintain documentation automatically
|
||||
- Run scheduled code quality checks
|
||||
- Respond to slash commands in issues and PRs
|
||||
- Orchestrate multi-step repository automation
|
||||
|
||||
| Name | Description | Triggers |
|
||||
| ---- | ----------- | -------- |
|
||||
| [Daily Issues Report](../workflows/daily-issues-report.md) | Generates a daily summary of open issues and recent activity as a GitHub issue | schedule |
|
||||
| [OSPO Contributors Report](../workflows/ospo-contributors-report.md) | Monthly contributor activity metrics across an organization's repositories. | schedule, workflow_dispatch |
|
||||
| [OSPO Organization Health Report](../workflows/ospo-org-health.md) | Comprehensive weekly health report for a GitHub organization. Surfaces stale issues/PRs, merge time analysis, contributor leaderboards, and actionable items needing human attention. | schedule, workflow_dispatch |
|
||||
| [OSPO Stale Repository Report](../workflows/ospo-stale-repos.md) | Identifies inactive repositories in your organization and generates an archival recommendation report. | schedule, workflow_dispatch |
|
||||
| [OSS Release Compliance Checker](../workflows/ospo-release-compliance-checker.md) | Analyzes a target repository against open source release requirements and posts a detailed compliance report as an issue comment. | issues, workflow_dispatch |
|
||||
62
eng/clean-materialized-plugins.mjs
Normal file
62
eng/clean-materialized-plugins.mjs
Normal file
@@ -0,0 +1,62 @@
|
||||
#!/usr/bin/env node
|
||||
|
||||
import fs from "fs";
|
||||
import path from "path";
|
||||
import { ROOT_FOLDER } from "./constants.mjs";
|
||||
|
||||
const PLUGINS_DIR = path.join(ROOT_FOLDER, "plugins");
|
||||
const MATERIALIZED_DIRS = ["agents", "commands", "skills"];
|
||||
|
||||
function cleanPlugin(pluginPath) {
|
||||
let removed = 0;
|
||||
for (const subdir of MATERIALIZED_DIRS) {
|
||||
const target = path.join(pluginPath, subdir);
|
||||
if (fs.existsSync(target) && fs.statSync(target).isDirectory()) {
|
||||
const count = countFiles(target);
|
||||
fs.rmSync(target, { recursive: true, force: true });
|
||||
removed += count;
|
||||
console.log(` Removed ${path.basename(pluginPath)}/${subdir}/ (${count} files)`);
|
||||
}
|
||||
}
|
||||
return removed;
|
||||
}
|
||||
|
||||
function countFiles(dir) {
|
||||
let count = 0;
|
||||
for (const entry of fs.readdirSync(dir, { withFileTypes: true })) {
|
||||
if (entry.isDirectory()) {
|
||||
count += countFiles(path.join(dir, entry.name));
|
||||
} else {
|
||||
count++;
|
||||
}
|
||||
}
|
||||
return count;
|
||||
}
|
||||
|
||||
function main() {
|
||||
console.log("Cleaning materialized files from plugins...\n");
|
||||
|
||||
if (!fs.existsSync(PLUGINS_DIR)) {
|
||||
console.error(`Error: plugins directory not found at ${PLUGINS_DIR}`);
|
||||
process.exit(1);
|
||||
}
|
||||
|
||||
const pluginDirs = fs.readdirSync(PLUGINS_DIR, { withFileTypes: true })
|
||||
.filter(entry => entry.isDirectory())
|
||||
.map(entry => entry.name)
|
||||
.sort();
|
||||
|
||||
let total = 0;
|
||||
for (const dirName of pluginDirs) {
|
||||
total += cleanPlugin(path.join(PLUGINS_DIR, dirName));
|
||||
}
|
||||
|
||||
console.log();
|
||||
if (total === 0) {
|
||||
console.log("✅ No materialized files found. Plugins are already clean.");
|
||||
} else {
|
||||
console.log(`✅ Removed ${total} materialized file(s) from plugins.`);
|
||||
}
|
||||
}
|
||||
|
||||
main();
|
||||
@@ -10,7 +10,11 @@ const TEMPLATES = {
|
||||
|
||||
Team and project-specific instructions to enhance GitHub Copilot's behavior for specific technologies and coding practices.`,
|
||||
|
||||
instructionsUsage: `### How to Use Custom Instructions
|
||||
instructionsUsage: `### How to Contribute
|
||||
|
||||
See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-instructions) for guidelines on how to contribute new instructions, improve existing ones, and share your use cases.
|
||||
|
||||
### How to Use Custom Instructions
|
||||
|
||||
**To Install:**
|
||||
- Click the **VS Code** or **VS Code Insiders** install button for the instruction you want to use
|
||||
@@ -21,31 +25,20 @@ Team and project-specific instructions to enhance GitHub Copilot's behavior for
|
||||
- Create task-specific \`*.instructions.md\` files in your workspace's \`.github/instructions/\` folder (e.g., \`.github/instructions/my-csharp-rules.instructions.md\`)
|
||||
- Instructions automatically apply to Copilot behavior once installed in your workspace`,
|
||||
|
||||
promptsSection: `## 🎯 Reusable Prompts
|
||||
|
||||
Ready-to-use prompt templates for specific development scenarios and tasks, defining prompt text with a specific mode, model, and available set of tools.`,
|
||||
|
||||
promptsUsage: `### How to Use Reusable Prompts
|
||||
|
||||
**To Install:**
|
||||
- Click the **VS Code** or **VS Code Insiders** install button for the prompt you want to use
|
||||
- Download the \`*.prompt.md\` file and manually add it to your prompt collection
|
||||
|
||||
**To Run/Execute:**
|
||||
- Use \`/prompt-name\` in VS Code chat after installation
|
||||
- Run the \`Chat: Run Prompt\` command from the Command Palette
|
||||
- Hit the run button while you have a prompt file open in VS Code`,
|
||||
|
||||
pluginsSection: `## 🔌 Plugins
|
||||
|
||||
Curated plugins of related prompts, agents, and skills organized around specific themes, workflows, or use cases. Plugins can be installed directly via GitHub Copilot CLI.`,
|
||||
Curated plugins of related agents and skills organized around specific themes, workflows, or use cases. Plugins can be installed directly via GitHub Copilot CLI.`,
|
||||
|
||||
pluginsUsage: `### How to Use Plugins
|
||||
pluginsUsage: `### How to Contribute
|
||||
|
||||
See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-plugins) for guidelines on how to contribute new plugins, improve existing ones, and share your use cases.
|
||||
|
||||
### How to Use Plugins
|
||||
|
||||
**Browse Plugins:**
|
||||
- ⭐ Featured plugins are highlighted and appear at the top of the list
|
||||
- Explore themed plugins that group related customizations
|
||||
- Each plugin includes prompts, agents, and skills for specific workflows
|
||||
- Each plugin includes agents and skills for specific workflows
|
||||
- Plugins make it easy to adopt comprehensive toolkits for particular scenarios
|
||||
|
||||
**Install Plugins:**
|
||||
@@ -55,13 +48,17 @@ Curated plugins of related prompts, agents, and skills organized around specific
|
||||
|
||||
featuredPluginsSection: `## 🌟 Featured Plugins
|
||||
|
||||
Discover our curated plugins of prompts, agents, and skills organized around specific themes and workflows.`,
|
||||
Discover our curated plugins of agents and skills organized around specific themes and workflows.`,
|
||||
|
||||
agentsSection: `## 🤖 Custom Agents
|
||||
|
||||
Custom agents for GitHub Copilot, making it easy for users and organizations to "specialize" their Copilot coding agent (CCA) through simple file-based configuration.`,
|
||||
|
||||
agentsUsage: `### How to Use Custom Agents
|
||||
agentsUsage: `### How to Contribute
|
||||
|
||||
See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-agents) for guidelines on how to contribute new agents, improve existing ones, and share your use cases.
|
||||
|
||||
### How to Use Custom Agents
|
||||
|
||||
**To Install:**
|
||||
- Click the **VS Code** or **VS Code Insiders** install button for the agent you want to use
|
||||
@@ -83,7 +80,11 @@ Agent Skills are self-contained folders with instructions and bundled resources
|
||||
|
||||
Skills differ from other primitives by supporting bundled assets (scripts, code samples, reference data) that agents can utilize when performing specialized tasks.`,
|
||||
|
||||
skillsUsage: `### How to Use Agent Skills
|
||||
skillsUsage: `### How to Contribute
|
||||
|
||||
See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to contribute new agent skills, improve existing ones, and share your use cases.
|
||||
|
||||
### How to Use Agent Skills
|
||||
|
||||
**What's Included:**
|
||||
- Each skill is a folder containing a \`SKILL.md\` instruction file
|
||||
@@ -104,7 +105,11 @@ Skills differ from other primitives by supporting bundled assets (scripts, code
|
||||
|
||||
Hooks enable automated workflows triggered by specific events during GitHub Copilot coding agent sessions, such as session start, session end, user prompts, and tool usage.`,
|
||||
|
||||
hooksUsage: `### How to Use Hooks
|
||||
hooksUsage: `### How to Contribute
|
||||
|
||||
See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-hooks) for guidelines on how to contribute new hooks, improve existing ones, and share your use cases.
|
||||
|
||||
### How to Use Hooks
|
||||
|
||||
**What's Included:**
|
||||
- Each hook is a folder containing a \`README.md\` file and a \`hooks.json\` configuration
|
||||
@@ -127,6 +132,40 @@ Hooks enable automated workflows triggered by specific events during GitHub Copi
|
||||
- Track usage analytics
|
||||
- Integrate with external tools and services
|
||||
- Custom session workflows`,
|
||||
|
||||
workflowsSection: `## ⚡ Agentic Workflows
|
||||
|
||||
[Agentic Workflows](https://github.github.com/gh-aw) are AI-powered repository automations that run coding agents in GitHub Actions. Defined in markdown with natural language instructions, they enable event-triggered and scheduled automation with built-in guardrails and security-first design.`,
|
||||
|
||||
workflowsUsage: `### How to Contribute
|
||||
|
||||
See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-agentic-workflows) for guidelines on how to contribute new workflows, improve existing ones, and share your use cases.
|
||||
|
||||
### How to Use Agentic Workflows
|
||||
|
||||
**What's Included:**
|
||||
- Each workflow is a single \`.md\` file with YAML frontmatter and natural language instructions
|
||||
- Workflows are compiled to \`.lock.yml\` GitHub Actions files via \`gh aw compile\`
|
||||
- Workflows follow the [GitHub Agentic Workflows specification](https://github.github.com/gh-aw)
|
||||
|
||||
**To Install:**
|
||||
- Install the \`gh aw\` CLI extension: \`gh extension install github/gh-aw\`
|
||||
- Copy the workflow \`.md\` file to your repository's \`.github/workflows/\` directory
|
||||
- Compile with \`gh aw compile\` to generate the \`.lock.yml\` file
|
||||
- Commit both the \`.md\` and \`.lock.yml\` files
|
||||
|
||||
**To Activate/Use:**
|
||||
- Workflows run automatically based on their configured triggers (schedules, events, slash commands)
|
||||
- Use \`gh aw run <workflow>\` to trigger a manual run
|
||||
- Monitor runs with \`gh aw status\` and \`gh aw logs\`
|
||||
|
||||
**When to Use:**
|
||||
- Automate issue triage and labeling
|
||||
- Generate daily status reports
|
||||
- Maintain documentation automatically
|
||||
- Run scheduled code quality checks
|
||||
- Respond to slash commands in issues and PRs
|
||||
- Orchestrate multi-step repository automation`,
|
||||
};
|
||||
|
||||
const vscodeInstallImage =
|
||||
@@ -140,18 +179,17 @@ const repoBaseUrl =
|
||||
|
||||
const AKA_INSTALL_URLS = {
|
||||
instructions: "https://aka.ms/awesome-copilot/install/instructions",
|
||||
prompt: "https://aka.ms/awesome-copilot/install/prompt",
|
||||
agent: "https://aka.ms/awesome-copilot/install/agent",
|
||||
hook: "https://aka.ms/awesome-copilot/install/hook",
|
||||
};
|
||||
|
||||
const ROOT_FOLDER = path.join(__dirname, "..");
|
||||
const INSTRUCTIONS_DIR = path.join(ROOT_FOLDER, "instructions");
|
||||
const PROMPTS_DIR = path.join(ROOT_FOLDER, "prompts");
|
||||
const AGENTS_DIR = path.join(ROOT_FOLDER, "agents");
|
||||
const SKILLS_DIR = path.join(ROOT_FOLDER, "skills");
|
||||
const HOOKS_DIR = path.join(ROOT_FOLDER, "hooks");
|
||||
const PLUGINS_DIR = path.join(ROOT_FOLDER, "plugins");
|
||||
const WORKFLOWS_DIR = path.join(ROOT_FOLDER, "workflows");
|
||||
const COOKBOOK_DIR = path.join(ROOT_FOLDER, "cookbook");
|
||||
const MAX_PLUGIN_ITEMS = 50;
|
||||
|
||||
@@ -166,13 +204,12 @@ const DOCS_DIR = path.join(ROOT_FOLDER, "docs");
|
||||
export {
|
||||
AGENTS_DIR,
|
||||
AKA_INSTALL_URLS,
|
||||
PLUGINS_DIR,
|
||||
COOKBOOK_DIR,
|
||||
DOCS_DIR,
|
||||
HOOKS_DIR,
|
||||
INSTRUCTIONS_DIR,
|
||||
MAX_PLUGIN_ITEMS,
|
||||
PROMPTS_DIR,
|
||||
PLUGINS_DIR,
|
||||
repoBaseUrl,
|
||||
ROOT_FOLDER,
|
||||
SKILL_DESCRIPTION_MAX_LENGTH,
|
||||
@@ -182,6 +219,6 @@ export {
|
||||
SKILLS_DIR,
|
||||
TEMPLATES,
|
||||
vscodeInsidersInstallImage,
|
||||
vscodeInstallImage
|
||||
vscodeInstallImage,
|
||||
WORKFLOWS_DIR,
|
||||
};
|
||||
|
||||
|
||||
@@ -30,9 +30,6 @@ export const TYPE_PATTERNS = {
|
||||
instructions: [
|
||||
'instructions/*.instructions.md'
|
||||
],
|
||||
prompts: [
|
||||
'prompts/*.prompt.md'
|
||||
],
|
||||
agents: [
|
||||
'chatmodes/*.chatmode.md',
|
||||
'agents/*.agent.md'
|
||||
@@ -140,7 +137,7 @@ export const isAutoGeneratedFile = (filePath) => {
|
||||
};
|
||||
|
||||
/**
|
||||
* Infer a contribution type string (e.g. 'prompts', 'agents', 'doc') for a file path.
|
||||
* Infer a contribution type string (e.g. 'skills', 'agents', 'doc') for a file path.
|
||||
* Returns null if no specific type matched.
|
||||
* @param {string} filePath
|
||||
* @returns {string|null}
|
||||
|
||||
@@ -14,12 +14,12 @@ const MARKETPLACE_FILE = path.join(ROOT_FOLDER, ".github/plugin", "marketplace.j
|
||||
*/
|
||||
function readPluginMetadata(pluginDir) {
|
||||
const pluginJsonPath = path.join(pluginDir, ".github/plugin", "plugin.json");
|
||||
|
||||
|
||||
if (!fs.existsSync(pluginJsonPath)) {
|
||||
console.warn(`Warning: No plugin.json found for ${path.basename(pluginDir)}`);
|
||||
return null;
|
||||
}
|
||||
|
||||
|
||||
try {
|
||||
const content = fs.readFileSync(pluginJsonPath, "utf8");
|
||||
return JSON.parse(content);
|
||||
@@ -34,30 +34,30 @@ function readPluginMetadata(pluginDir) {
|
||||
*/
|
||||
function generateMarketplace() {
|
||||
console.log("Generating marketplace.json...");
|
||||
|
||||
|
||||
if (!fs.existsSync(PLUGINS_DIR)) {
|
||||
console.error(`Error: Plugins directory not found at ${PLUGINS_DIR}`);
|
||||
process.exit(1);
|
||||
}
|
||||
|
||||
|
||||
// Read all plugin directories
|
||||
const pluginDirs = fs.readdirSync(PLUGINS_DIR, { withFileTypes: true })
|
||||
.filter(entry => entry.isDirectory())
|
||||
.map(entry => entry.name)
|
||||
.sort();
|
||||
|
||||
|
||||
console.log(`Found ${pluginDirs.length} plugin directories`);
|
||||
|
||||
|
||||
// Read metadata for each plugin
|
||||
const plugins = [];
|
||||
for (const dirName of pluginDirs) {
|
||||
const pluginPath = path.join(PLUGINS_DIR, dirName);
|
||||
const metadata = readPluginMetadata(pluginPath);
|
||||
|
||||
|
||||
if (metadata) {
|
||||
plugins.push({
|
||||
name: metadata.name,
|
||||
source: `./plugins/${dirName}`,
|
||||
source: dirName,
|
||||
description: metadata.description,
|
||||
version: metadata.version || "1.0.0"
|
||||
});
|
||||
@@ -66,7 +66,7 @@ function generateMarketplace() {
|
||||
console.log(`✗ Skipped: ${dirName} (no valid plugin.json)`);
|
||||
}
|
||||
}
|
||||
|
||||
|
||||
// Create marketplace.json structure
|
||||
const marketplace = {
|
||||
name: "awesome-copilot",
|
||||
@@ -81,16 +81,16 @@ function generateMarketplace() {
|
||||
},
|
||||
plugins: plugins
|
||||
};
|
||||
|
||||
|
||||
// Ensure directory exists
|
||||
const marketplaceDir = path.dirname(MARKETPLACE_FILE);
|
||||
if (!fs.existsSync(marketplaceDir)) {
|
||||
fs.mkdirSync(marketplaceDir, { recursive: true });
|
||||
}
|
||||
|
||||
|
||||
// Write marketplace.json
|
||||
fs.writeFileSync(MARKETPLACE_FILE, JSON.stringify(marketplace, null, 2) + "\n");
|
||||
|
||||
|
||||
console.log(`\n✓ Successfully generated marketplace.json with ${plugins.length} plugins`);
|
||||
console.log(` Location: ${MARKETPLACE_FILE}`);
|
||||
}
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
/**
|
||||
* Generate JSON metadata files for the GitHub Pages website.
|
||||
* This script extracts metadata from agents, prompts, instructions, skills, and plugins
|
||||
* This script extracts metadata from agents, instructions, skills, hooks, and plugins
|
||||
* and writes them to website/data/ for client-side search and display.
|
||||
*/
|
||||
|
||||
@@ -10,21 +10,22 @@ import fs from "fs";
|
||||
import path from "path";
|
||||
import { fileURLToPath } from "url";
|
||||
import {
|
||||
AGENTS_DIR,
|
||||
COOKBOOK_DIR,
|
||||
HOOKS_DIR,
|
||||
INSTRUCTIONS_DIR,
|
||||
PLUGINS_DIR,
|
||||
PROMPTS_DIR,
|
||||
ROOT_FOLDER,
|
||||
SKILLS_DIR
|
||||
AGENTS_DIR,
|
||||
COOKBOOK_DIR,
|
||||
HOOKS_DIR,
|
||||
INSTRUCTIONS_DIR,
|
||||
PLUGINS_DIR,
|
||||
ROOT_FOLDER,
|
||||
SKILLS_DIR,
|
||||
WORKFLOWS_DIR,
|
||||
} from "./constants.mjs";
|
||||
import { getGitFileDates } from "./utils/git-dates.mjs";
|
||||
import {
|
||||
parseFrontmatter,
|
||||
parseSkillMetadata,
|
||||
parseHookMetadata,
|
||||
parseYamlFile,
|
||||
parseFrontmatter,
|
||||
parseHookMetadata,
|
||||
parseSkillMetadata,
|
||||
parseWorkflowMetadata,
|
||||
parseYamlFile,
|
||||
} from "./yaml-parser.mjs";
|
||||
|
||||
const __filename = fileURLToPath(import.meta.url);
|
||||
@@ -131,7 +132,7 @@ function generateAgentsData(gitDates) {
|
||||
*/
|
||||
function generateHooksData(gitDates) {
|
||||
const hooks = [];
|
||||
|
||||
|
||||
// Check if hooks directory exists
|
||||
if (!fs.existsSync(HOOKS_DIR)) {
|
||||
return {
|
||||
@@ -193,46 +194,56 @@ function generateHooksData(gitDates) {
|
||||
}
|
||||
|
||||
/**
|
||||
* Generate prompts metadata
|
||||
* Generate workflows metadata (flat .md files)
|
||||
*/
|
||||
function generatePromptsData(gitDates) {
|
||||
const prompts = [];
|
||||
const files = fs
|
||||
.readdirSync(PROMPTS_DIR)
|
||||
.filter((f) => f.endsWith(".prompt.md"));
|
||||
function generateWorkflowsData(gitDates) {
|
||||
const workflows = [];
|
||||
|
||||
// Track all unique tools for filters
|
||||
const allTools = new Set();
|
||||
if (!fs.existsSync(WORKFLOWS_DIR)) {
|
||||
return {
|
||||
items: workflows,
|
||||
filters: {
|
||||
triggers: [],
|
||||
},
|
||||
};
|
||||
}
|
||||
|
||||
const workflowFiles = fs.readdirSync(WORKFLOWS_DIR).filter((file) => {
|
||||
return file.endsWith(".md") && file !== ".gitkeep";
|
||||
});
|
||||
|
||||
const allTriggers = new Set();
|
||||
|
||||
for (const file of workflowFiles) {
|
||||
const filePath = path.join(WORKFLOWS_DIR, file);
|
||||
const metadata = parseWorkflowMetadata(filePath);
|
||||
if (!metadata) continue;
|
||||
|
||||
for (const file of files) {
|
||||
const filePath = path.join(PROMPTS_DIR, file);
|
||||
const frontmatter = parseFrontmatter(filePath);
|
||||
const relativePath = path
|
||||
.relative(ROOT_FOLDER, filePath)
|
||||
.replace(/\\/g, "/");
|
||||
|
||||
const tools = frontmatter?.tools || [];
|
||||
tools.forEach((t) => allTools.add(t));
|
||||
(metadata.triggers || []).forEach((t) => allTriggers.add(t));
|
||||
|
||||
prompts.push({
|
||||
id: file.replace(".prompt.md", ""),
|
||||
title: extractTitle(filePath, frontmatter),
|
||||
description: frontmatter?.description || "",
|
||||
agent: frontmatter?.agent || null,
|
||||
model: frontmatter?.model || null,
|
||||
tools: tools,
|
||||
const id = path.basename(file, ".md");
|
||||
workflows.push({
|
||||
id,
|
||||
title: metadata.name,
|
||||
description: metadata.description,
|
||||
triggers: metadata.triggers || [],
|
||||
path: relativePath,
|
||||
filename: file,
|
||||
lastUpdated: gitDates.get(relativePath) || null,
|
||||
});
|
||||
}
|
||||
|
||||
const sortedPrompts = prompts.sort((a, b) => a.title.localeCompare(b.title));
|
||||
const sortedWorkflows = workflows.sort((a, b) =>
|
||||
a.title.localeCompare(b.title)
|
||||
);
|
||||
|
||||
return {
|
||||
items: sortedPrompts,
|
||||
items: sortedWorkflows,
|
||||
filters: {
|
||||
tools: Array.from(allTools).sort(),
|
||||
triggers: Array.from(allTriggers).sort(),
|
||||
},
|
||||
};
|
||||
}
|
||||
@@ -491,8 +502,9 @@ function generatePluginsData(gitDates) {
|
||||
return { items: [], filters: { tags: [] } };
|
||||
}
|
||||
|
||||
const pluginDirs = fs.readdirSync(PLUGINS_DIR, { withFileTypes: true })
|
||||
.filter(d => d.isDirectory());
|
||||
const pluginDirs = fs
|
||||
.readdirSync(PLUGINS_DIR, { withFileTypes: true })
|
||||
.filter((d) => d.isDirectory());
|
||||
|
||||
for (const dir of pluginDirs) {
|
||||
const pluginDir = path.join(PLUGINS_DIR, dir.name);
|
||||
@@ -507,9 +519,9 @@ function generatePluginsData(gitDates) {
|
||||
|
||||
// Build items list from spec fields (agents, commands, skills)
|
||||
const items = [
|
||||
...(data.agents || []).map(p => ({ kind: "agent", path: p })),
|
||||
...(data.commands || []).map(p => ({ kind: "prompt", path: p })),
|
||||
...(data.skills || []).map(p => ({ kind: "skill", path: p })),
|
||||
...(data.agents || []).map((p) => ({ kind: "agent", path: p })),
|
||||
...(data.commands || []).map((p) => ({ kind: "prompt", path: p })),
|
||||
...(data.skills || []).map((p) => ({ kind: "skill", path: p })),
|
||||
];
|
||||
|
||||
const tags = data.keywords || data.tags || [];
|
||||
@@ -523,7 +535,9 @@ function generatePluginsData(gitDates) {
|
||||
itemCount: items.length,
|
||||
items: items,
|
||||
lastUpdated: dates.lastModified || null,
|
||||
searchText: `${data.name || dir.name} ${data.description || ""} ${tags.join(" ")}`.toLowerCase(),
|
||||
searchText: `${data.name || dir.name} ${
|
||||
data.description || ""
|
||||
} ${tags.join(" ")}`.toLowerCase(),
|
||||
});
|
||||
} catch (e) {
|
||||
console.warn(`Failed to parse plugin: ${dir.name}`, e.message);
|
||||
@@ -531,13 +545,13 @@ function generatePluginsData(gitDates) {
|
||||
}
|
||||
|
||||
// Collect all unique tags
|
||||
const allTags = [...new Set(plugins.flatMap(p => p.tags))].sort();
|
||||
const allTags = [...new Set(plugins.flatMap((p) => p.tags))].sort();
|
||||
|
||||
const sortedPlugins = plugins.sort((a, b) => a.name.localeCompare(b.name));
|
||||
|
||||
return {
|
||||
items: sortedPlugins,
|
||||
filters: { tags: allTags }
|
||||
filters: { tags: allTags },
|
||||
};
|
||||
}
|
||||
|
||||
@@ -603,9 +617,9 @@ function generateToolsData() {
|
||||
*/
|
||||
function generateSearchIndex(
|
||||
agents,
|
||||
prompts,
|
||||
instructions,
|
||||
hooks,
|
||||
workflows,
|
||||
skills,
|
||||
plugins
|
||||
) {
|
||||
@@ -625,18 +639,6 @@ function generateSearchIndex(
|
||||
});
|
||||
}
|
||||
|
||||
for (const prompt of prompts) {
|
||||
index.push({
|
||||
type: "prompt",
|
||||
id: prompt.id,
|
||||
title: prompt.title,
|
||||
description: prompt.description,
|
||||
path: prompt.path,
|
||||
lastUpdated: prompt.lastUpdated,
|
||||
searchText: `${prompt.title} ${prompt.description}`.toLowerCase(),
|
||||
});
|
||||
}
|
||||
|
||||
for (const instruction of instructions) {
|
||||
index.push({
|
||||
type: "instruction",
|
||||
@@ -665,6 +667,20 @@ function generateSearchIndex(
|
||||
});
|
||||
}
|
||||
|
||||
for (const workflow of workflows) {
|
||||
index.push({
|
||||
type: "workflow",
|
||||
id: workflow.id,
|
||||
title: workflow.title,
|
||||
description: workflow.description,
|
||||
path: workflow.path,
|
||||
lastUpdated: workflow.lastUpdated,
|
||||
searchText: `${workflow.title} ${
|
||||
workflow.description
|
||||
} ${workflow.triggers.join(" ")}`.toLowerCase(),
|
||||
});
|
||||
}
|
||||
|
||||
for (const skill of skills) {
|
||||
index.push({
|
||||
type: "skill",
|
||||
@@ -799,7 +815,7 @@ async function main() {
|
||||
// Load git dates for all resource files (single efficient git command)
|
||||
console.log("Loading git history for last updated dates...");
|
||||
const gitDates = getGitFileDates(
|
||||
["agents/", "prompts/", "instructions/", "hooks/", "skills/", "plugins/"],
|
||||
["agents/", "instructions/", "hooks/", "workflows/", "skills/", "plugins/"],
|
||||
ROOT_FOLDER
|
||||
);
|
||||
console.log(`✓ Loaded dates for ${gitDates.size} files\n`);
|
||||
@@ -817,10 +833,10 @@ async function main() {
|
||||
`✓ Generated ${hooks.length} hooks (${hooksData.filters.hooks.length} hook types, ${hooksData.filters.tags.length} tags)`
|
||||
);
|
||||
|
||||
const promptsData = generatePromptsData(gitDates);
|
||||
const prompts = promptsData.items;
|
||||
const workflowsData = generateWorkflowsData(gitDates);
|
||||
const workflows = workflowsData.items;
|
||||
console.log(
|
||||
`✓ Generated ${prompts.length} prompts (${promptsData.filters.tools.length} tools)`
|
||||
`✓ Generated ${workflows.length} workflows (${workflowsData.filters.triggers.length} triggers)`
|
||||
);
|
||||
|
||||
const instructionsData = generateInstructionsData(gitDates);
|
||||
@@ -854,9 +870,9 @@ async function main() {
|
||||
|
||||
const searchIndex = generateSearchIndex(
|
||||
agents,
|
||||
prompts,
|
||||
instructions,
|
||||
hooks,
|
||||
workflows,
|
||||
skills,
|
||||
plugins
|
||||
);
|
||||
@@ -874,8 +890,8 @@ async function main() {
|
||||
);
|
||||
|
||||
fs.writeFileSync(
|
||||
path.join(WEBSITE_DATA_DIR, "prompts.json"),
|
||||
JSON.stringify(promptsData, null, 2)
|
||||
path.join(WEBSITE_DATA_DIR, "workflows.json"),
|
||||
JSON.stringify(workflowsData, null, 2)
|
||||
);
|
||||
|
||||
fs.writeFileSync(
|
||||
@@ -913,10 +929,10 @@ async function main() {
|
||||
generated: new Date().toISOString(),
|
||||
counts: {
|
||||
agents: agents.length,
|
||||
prompts: prompts.length,
|
||||
instructions: instructions.length,
|
||||
skills: skills.length,
|
||||
hooks: hooks.length,
|
||||
workflows: workflows.length,
|
||||
plugins: plugins.length,
|
||||
tools: tools.length,
|
||||
samples: samplesData.totalRecipes,
|
||||
|
||||
@@ -26,7 +26,6 @@ function copyDirRecursive(src, dest) {
|
||||
* Resolve a plugin-relative path to the repo-root source file.
|
||||
*
|
||||
* ./agents/foo.md → ROOT/agents/foo.agent.md
|
||||
* ./commands/bar.md → ROOT/prompts/bar.prompt.md
|
||||
* ./skills/baz/ → ROOT/skills/baz/
|
||||
*/
|
||||
function resolveSource(relPath) {
|
||||
@@ -34,9 +33,6 @@ function resolveSource(relPath) {
|
||||
if (relPath.startsWith("./agents/")) {
|
||||
return path.join(ROOT_FOLDER, "agents", `${basename}.agent.md`);
|
||||
}
|
||||
if (relPath.startsWith("./commands/")) {
|
||||
return path.join(ROOT_FOLDER, "prompts", `${basename}.prompt.md`);
|
||||
}
|
||||
if (relPath.startsWith("./skills/")) {
|
||||
// Strip trailing slash and get the skill folder name
|
||||
const skillName = relPath.replace(/^\.\/skills\//, "").replace(/\/$/, "");
|
||||
@@ -59,7 +55,6 @@ function materializePlugins() {
|
||||
.sort();
|
||||
|
||||
let totalAgents = 0;
|
||||
let totalCommands = 0;
|
||||
let totalSkills = 0;
|
||||
let warnings = 0;
|
||||
let errors = 0;
|
||||
@@ -104,27 +99,6 @@ function materializePlugins() {
|
||||
}
|
||||
}
|
||||
|
||||
// Process commands
|
||||
if (Array.isArray(metadata.commands)) {
|
||||
for (const relPath of metadata.commands) {
|
||||
const src = resolveSource(relPath);
|
||||
if (!src) {
|
||||
console.warn(` ⚠ ${pluginName}: Unknown path format: ${relPath}`);
|
||||
warnings++;
|
||||
continue;
|
||||
}
|
||||
if (!fs.existsSync(src)) {
|
||||
console.warn(` ⚠ ${pluginName}: Source not found: ${src}`);
|
||||
warnings++;
|
||||
continue;
|
||||
}
|
||||
const dest = path.join(pluginPath, relPath.replace(/^\.\//, ""));
|
||||
fs.mkdirSync(path.dirname(dest), { recursive: true });
|
||||
fs.copyFileSync(src, dest);
|
||||
totalCommands++;
|
||||
}
|
||||
}
|
||||
|
||||
// Process skills
|
||||
if (Array.isArray(metadata.skills)) {
|
||||
for (const relPath of metadata.skills) {
|
||||
@@ -145,16 +119,39 @@ function materializePlugins() {
|
||||
}
|
||||
}
|
||||
|
||||
// Rewrite plugin.json to use folder paths instead of individual file paths.
|
||||
// On staged, paths like ./agents/foo.md point to individual source files.
|
||||
// On main, after materialization, we only need the containing directory.
|
||||
const rewritten = { ...metadata };
|
||||
let changed = false;
|
||||
|
||||
for (const field of ["agents", "commands"]) {
|
||||
if (Array.isArray(rewritten[field]) && rewritten[field].length > 0) {
|
||||
const dirs = [...new Set(rewritten[field].map(p => path.dirname(p)))];
|
||||
rewritten[field] = dirs;
|
||||
changed = true;
|
||||
}
|
||||
}
|
||||
|
||||
if (Array.isArray(rewritten.skills) && rewritten.skills.length > 0) {
|
||||
// Skills are already folder refs (./skills/name/); strip trailing slash
|
||||
rewritten.skills = rewritten.skills.map(p => p.replace(/\/$/, ""));
|
||||
changed = true;
|
||||
}
|
||||
|
||||
if (changed) {
|
||||
fs.writeFileSync(pluginJsonPath, JSON.stringify(rewritten, null, 2) + "\n", "utf8");
|
||||
}
|
||||
|
||||
const counts = [];
|
||||
if (metadata.agents?.length) counts.push(`${metadata.agents.length} agents`);
|
||||
if (metadata.commands?.length) counts.push(`${metadata.commands.length} commands`);
|
||||
if (metadata.skills?.length) counts.push(`${metadata.skills.length} skills`);
|
||||
if (counts.length) {
|
||||
console.log(`✓ ${pluginName}: ${counts.join(", ")}`);
|
||||
}
|
||||
}
|
||||
|
||||
console.log(`\nDone. Copied ${totalAgents} agents, ${totalCommands} commands, ${totalSkills} skills.`);
|
||||
console.log(`\nDone. Copied ${totalAgents} agents, ${totalSkills} skills.`);
|
||||
if (warnings > 0) {
|
||||
console.log(`${warnings} warning(s).`);
|
||||
}
|
||||
|
||||
137
eng/migrate-prompts-to-skills.mjs
Executable file
137
eng/migrate-prompts-to-skills.mjs
Executable file
@@ -0,0 +1,137 @@
|
||||
#!/usr/bin/env node
|
||||
|
||||
import fs from "fs";
|
||||
import path from "path";
|
||||
import { ROOT_FOLDER, SKILLS_DIR } from "./constants.mjs";
|
||||
import { parseFrontmatter } from "./yaml-parser.mjs";
|
||||
|
||||
const PROMPTS_DIR = path.join(ROOT_FOLDER, "prompts");
|
||||
/**
|
||||
* Convert a prompt file to a skill folder
|
||||
* @param {string} promptFilePath - Full path to the prompt file
|
||||
* @returns {object} Result with success status and details
|
||||
*/
|
||||
function convertPromptToSkill(promptFilePath) {
|
||||
const filename = path.basename(promptFilePath);
|
||||
const baseName = filename.replace(".prompt.md", "");
|
||||
|
||||
console.log(`\nConverting: ${baseName}`);
|
||||
|
||||
// Parse the prompt file frontmatter
|
||||
const frontmatter = parseFrontmatter(promptFilePath);
|
||||
const content = fs.readFileSync(promptFilePath, "utf8");
|
||||
|
||||
// Extract the content after frontmatter
|
||||
const frontmatterEndMatch = content.match(/^---\n[\s\S]*?\n---\n/);
|
||||
const mainContent = frontmatterEndMatch
|
||||
? content.substring(frontmatterEndMatch[0].length).trim()
|
||||
: content.trim();
|
||||
|
||||
// Create skill folder
|
||||
const skillFolderPath = path.join(SKILLS_DIR, baseName);
|
||||
if (fs.existsSync(skillFolderPath)) {
|
||||
console.log(` ⚠️ Skill folder already exists: ${baseName}`);
|
||||
return { success: false, reason: "already-exists", name: baseName };
|
||||
}
|
||||
|
||||
fs.mkdirSync(skillFolderPath, { recursive: true });
|
||||
|
||||
// Build new frontmatter for SKILL.md
|
||||
const skillFrontmatter = {
|
||||
name: baseName,
|
||||
description: frontmatter?.description || `Skill converted from ${filename}`,
|
||||
};
|
||||
|
||||
// Build SKILL.md content
|
||||
const skillContent = `---
|
||||
name: ${skillFrontmatter.name}
|
||||
description: '${skillFrontmatter.description.replace(/'/g, "'''")}'
|
||||
---
|
||||
|
||||
${mainContent}
|
||||
`;
|
||||
|
||||
// Write SKILL.md
|
||||
const skillFilePath = path.join(skillFolderPath, "SKILL.md");
|
||||
fs.writeFileSync(skillFilePath, skillContent, "utf8");
|
||||
|
||||
console.log(` ✓ Created skill: ${baseName}`);
|
||||
return { success: true, name: baseName, path: skillFolderPath };
|
||||
}
|
||||
|
||||
/**
|
||||
* Main migration function
|
||||
*/
|
||||
function main() {
|
||||
console.log("=".repeat(60));
|
||||
console.log("Starting Prompt to Skills Migration");
|
||||
console.log("=".repeat(60));
|
||||
|
||||
// Check if prompts directory exists
|
||||
if (!fs.existsSync(PROMPTS_DIR)) {
|
||||
console.error(`Error: Prompts directory not found: ${PROMPTS_DIR}`);
|
||||
process.exit(1);
|
||||
}
|
||||
|
||||
// Get all prompt files
|
||||
const promptFiles = fs
|
||||
.readdirSync(PROMPTS_DIR)
|
||||
.filter((file) => file.endsWith(".prompt.md"))
|
||||
.map((file) => path.join(PROMPTS_DIR, file));
|
||||
|
||||
console.log(`Found ${promptFiles.length} prompt files to convert\n`);
|
||||
|
||||
const results = {
|
||||
success: [],
|
||||
alreadyExists: [],
|
||||
failed: [],
|
||||
};
|
||||
|
||||
// Convert each prompt
|
||||
for (const promptFile of promptFiles) {
|
||||
try {
|
||||
const result = convertPromptToSkill(promptFile);
|
||||
if (result.success) {
|
||||
results.success.push(result.name);
|
||||
} else if (result.reason === "already-exists") {
|
||||
results.alreadyExists.push(result.name);
|
||||
} else {
|
||||
results.failed.push(result.name);
|
||||
}
|
||||
} catch (error) {
|
||||
const baseName = path.basename(promptFile, ".prompt.md");
|
||||
console.error(` ✗ Error converting ${baseName}: ${error.message}`);
|
||||
results.failed.push(baseName);
|
||||
}
|
||||
}
|
||||
|
||||
// Print summary
|
||||
console.log("\n" + "=".repeat(60));
|
||||
console.log("Migration Summary");
|
||||
console.log("=".repeat(60));
|
||||
console.log(`✓ Successfully converted: ${results.success.length}`);
|
||||
console.log(`⚠ Already existed: ${results.alreadyExists.length}`);
|
||||
console.log(`✗ Failed: ${results.failed.length}`);
|
||||
console.log(`Total processed: ${promptFiles.length}`);
|
||||
|
||||
if (results.failed.length > 0) {
|
||||
console.log("\nFailed conversions:");
|
||||
results.failed.forEach((name) => console.log(` - ${name}`));
|
||||
}
|
||||
|
||||
if (results.alreadyExists.length > 0) {
|
||||
console.log("\nSkipped (already exist):");
|
||||
results.alreadyExists.forEach((name) => console.log(` - ${name}`));
|
||||
}
|
||||
|
||||
console.log("\n✅ Migration complete!");
|
||||
console.log(
|
||||
"\nNext steps:\n" +
|
||||
"1. Run 'npm run skill:validate' to validate all new skills\n" +
|
||||
"2. Update plugin manifests to reference skills instead of commands\n" +
|
||||
"3. Remove prompts directory after testing\n"
|
||||
);
|
||||
}
|
||||
|
||||
// Run migration
|
||||
main();
|
||||
165
eng/update-plugin-commands-to-skills.mjs
Executable file
165
eng/update-plugin-commands-to-skills.mjs
Executable file
@@ -0,0 +1,165 @@
|
||||
#!/usr/bin/env node
|
||||
|
||||
import fs from "fs";
|
||||
import path from "path";
|
||||
import { PLUGINS_DIR } from "./constants.mjs";
|
||||
|
||||
/**
|
||||
* Convert commands references to skills references in a plugin.json
|
||||
* @param {string} pluginJsonPath - Path to the plugin.json file
|
||||
* @returns {object} Result with success status and details
|
||||
*/
|
||||
function updatePluginManifest(pluginJsonPath) {
|
||||
const pluginDir = path.dirname(path.dirname(path.dirname(pluginJsonPath)));
|
||||
const pluginName = path.basename(pluginDir);
|
||||
|
||||
console.log(`\nProcessing plugin: ${pluginName}`);
|
||||
|
||||
// Read and parse plugin.json
|
||||
let plugin;
|
||||
try {
|
||||
const content = fs.readFileSync(pluginJsonPath, "utf8");
|
||||
plugin = JSON.parse(content);
|
||||
} catch (error) {
|
||||
console.log(` ✗ Error reading/parsing: ${error.message}`);
|
||||
return { success: false, name: pluginName, reason: "parse-error" };
|
||||
}
|
||||
|
||||
// Check if plugin has commands field
|
||||
if (!plugin.commands || !Array.isArray(plugin.commands)) {
|
||||
console.log(` ℹ No commands field found`);
|
||||
return { success: false, name: pluginName, reason: "no-commands" };
|
||||
}
|
||||
|
||||
const commandCount = plugin.commands.length;
|
||||
console.log(` Found ${commandCount} command(s) to convert`);
|
||||
|
||||
// Validate and convert commands to skills format
|
||||
// Commands: "./commands/foo.md" → Skills: "./skills/foo/"
|
||||
const validCommands = plugin.commands.filter((cmd) => {
|
||||
if (typeof cmd !== "string") {
|
||||
console.log(` ⚠ Skipping non-string command entry: ${JSON.stringify(cmd)}`);
|
||||
return false;
|
||||
}
|
||||
if (!cmd.startsWith("./commands/") || !cmd.endsWith(".md")) {
|
||||
console.log(` ⚠ Skipping command with unexpected format: ${cmd}`);
|
||||
return false;
|
||||
}
|
||||
return true;
|
||||
});
|
||||
const skills = validCommands.map((cmd) => {
|
||||
const basename = path.basename(cmd, ".md");
|
||||
return `./skills/${basename}/`;
|
||||
});
|
||||
// Initialize skills array if it doesn't exist or is not an array
|
||||
if (!Array.isArray(plugin.skills)) {
|
||||
plugin.skills = [];
|
||||
}
|
||||
// Add converted commands to skills array, de-duplicating entries
|
||||
const allSkills = new Set(plugin.skills);
|
||||
for (const skillPath of skills) {
|
||||
allSkills.add(skillPath);
|
||||
}
|
||||
plugin.skills = Array.from(allSkills);
|
||||
|
||||
// Remove commands field
|
||||
delete plugin.commands;
|
||||
|
||||
// Write updated plugin.json
|
||||
try {
|
||||
fs.writeFileSync(
|
||||
pluginJsonPath,
|
||||
JSON.stringify(plugin, null, 2) + "\n",
|
||||
"utf8"
|
||||
);
|
||||
console.log(` ✓ Converted ${commandCount} command(s) to skills`);
|
||||
return { success: true, name: pluginName, count: commandCount };
|
||||
} catch (error) {
|
||||
console.log(` ✗ Error writing file: ${error.message}`);
|
||||
return { success: false, name: pluginName, reason: "write-error" };
|
||||
}
|
||||
}
|
||||
|
||||
/**
|
||||
* Main function to update all plugin manifests
|
||||
*/
|
||||
function main() {
|
||||
console.log("=".repeat(60));
|
||||
console.log("Updating Plugin Manifests: Commands → Skills");
|
||||
console.log("=".repeat(60));
|
||||
|
||||
// Check if plugins directory exists
|
||||
if (!fs.existsSync(PLUGINS_DIR)) {
|
||||
console.error(`Error: Plugins directory not found: ${PLUGINS_DIR}`);
|
||||
process.exit(1);
|
||||
}
|
||||
|
||||
// Find all plugin.json files
|
||||
const pluginDirs = fs
|
||||
.readdirSync(PLUGINS_DIR, { withFileTypes: true })
|
||||
.filter((entry) => entry.isDirectory())
|
||||
.map((entry) => entry.name);
|
||||
|
||||
console.log(`Found ${pluginDirs.length} plugin directory(ies)\n`);
|
||||
|
||||
const results = {
|
||||
updated: [],
|
||||
noCommands: [],
|
||||
failed: [],
|
||||
};
|
||||
|
||||
// Process each plugin
|
||||
for (const dirName of pluginDirs) {
|
||||
const pluginJsonPath = path.join(
|
||||
PLUGINS_DIR,
|
||||
dirName,
|
||||
".github/plugin",
|
||||
"plugin.json"
|
||||
);
|
||||
|
||||
if (!fs.existsSync(pluginJsonPath)) {
|
||||
console.log(`\nSkipping ${dirName}: no plugin.json found`);
|
||||
continue;
|
||||
}
|
||||
|
||||
const result = updatePluginManifest(pluginJsonPath);
|
||||
if (result.success) {
|
||||
results.updated.push({ name: result.name, count: result.count });
|
||||
} else if (result.reason === "no-commands") {
|
||||
results.noCommands.push(result.name);
|
||||
} else {
|
||||
results.failed.push(result.name);
|
||||
}
|
||||
}
|
||||
|
||||
// Print summary
|
||||
console.log("\n" + "=".repeat(60));
|
||||
console.log("Update Summary");
|
||||
console.log("=".repeat(60));
|
||||
console.log(`✓ Updated plugins: ${results.updated.length}`);
|
||||
console.log(`ℹ No commands field: ${results.noCommands.length}`);
|
||||
console.log(`✗ Failed: ${results.failed.length}`);
|
||||
console.log(`Total processed: ${pluginDirs.length}`);
|
||||
|
||||
if (results.updated.length > 0) {
|
||||
console.log("\nUpdated plugins:");
|
||||
results.updated.forEach(({ name, count }) =>
|
||||
console.log(` - ${name} (${count} command(s) → skills)`)
|
||||
);
|
||||
}
|
||||
|
||||
if (results.failed.length > 0) {
|
||||
console.log("\nFailed updates:");
|
||||
results.failed.forEach((name) => console.log(` - ${name}`));
|
||||
}
|
||||
|
||||
console.log("\n✅ Plugin manifest updates complete!");
|
||||
console.log(
|
||||
"\nNext steps:\n" +
|
||||
"1. Run 'npm run plugin:validate' to validate all updated plugins\n" +
|
||||
"2. Test that plugins work correctly\n"
|
||||
);
|
||||
}
|
||||
|
||||
// Run the update
|
||||
main();
|
||||
@@ -10,19 +10,20 @@ import {
|
||||
HOOKS_DIR,
|
||||
INSTRUCTIONS_DIR,
|
||||
PLUGINS_DIR,
|
||||
PROMPTS_DIR,
|
||||
repoBaseUrl,
|
||||
ROOT_FOLDER,
|
||||
SKILLS_DIR,
|
||||
TEMPLATES,
|
||||
vscodeInsidersInstallImage,
|
||||
vscodeInstallImage,
|
||||
WORKFLOWS_DIR,
|
||||
} from "./constants.mjs";
|
||||
import {
|
||||
extractMcpServerConfigs,
|
||||
parseFrontmatter,
|
||||
parseSkillMetadata,
|
||||
parseHookMetadata,
|
||||
parseWorkflowMetadata,
|
||||
} from "./yaml-parser.mjs";
|
||||
|
||||
const __filename = fileURLToPath(import.meta.url);
|
||||
@@ -341,63 +342,6 @@ function generateInstructionsSection(instructionsDir) {
|
||||
return `${TEMPLATES.instructionsSection}\n${TEMPLATES.instructionsUsage}\n\n${instructionsContent}`;
|
||||
}
|
||||
|
||||
/**
|
||||
* Generate the prompts section with a table of all prompts
|
||||
*/
|
||||
function generatePromptsSection(promptsDir) {
|
||||
// Check if directory exists
|
||||
if (!fs.existsSync(promptsDir)) {
|
||||
return "";
|
||||
}
|
||||
|
||||
// Get all prompt files
|
||||
const promptFiles = fs
|
||||
.readdirSync(promptsDir)
|
||||
.filter((file) => file.endsWith(".prompt.md"));
|
||||
|
||||
// Map prompt files to objects with title for sorting
|
||||
const promptEntries = promptFiles.map((file) => {
|
||||
const filePath = path.join(promptsDir, file);
|
||||
const title = extractTitle(filePath);
|
||||
return { file, filePath, title };
|
||||
});
|
||||
|
||||
// Sort by title alphabetically
|
||||
promptEntries.sort((a, b) => a.title.localeCompare(b.title));
|
||||
|
||||
console.log(`Found ${promptEntries.length} prompt files`);
|
||||
|
||||
// Return empty string if no files found
|
||||
if (promptEntries.length === 0) {
|
||||
return "";
|
||||
}
|
||||
|
||||
// Create table header
|
||||
let promptsContent = "| Title | Description |\n| ----- | ----------- |\n";
|
||||
|
||||
// Generate table rows for each prompt file
|
||||
for (const entry of promptEntries) {
|
||||
const { file, filePath, title } = entry;
|
||||
const link = encodeURI(`prompts/${file}`);
|
||||
|
||||
// Check if there's a description in the frontmatter
|
||||
const customDescription = extractDescription(filePath);
|
||||
|
||||
// Create badges for installation links
|
||||
const badges = makeBadges(link, "prompt");
|
||||
|
||||
if (customDescription && customDescription !== "null") {
|
||||
promptsContent += `| [${title}](../${link})<br />${badges} | ${formatTableCell(
|
||||
customDescription
|
||||
)} |\n`;
|
||||
} else {
|
||||
promptsContent += `| [${title}](../${link})<br />${badges} | | |\n`;
|
||||
}
|
||||
}
|
||||
|
||||
return `${TEMPLATES.promptsSection}\n${TEMPLATES.promptsUsage}\n\n${promptsContent}`;
|
||||
}
|
||||
|
||||
/**
|
||||
* Generate MCP server links for an agent
|
||||
* @param {string[]} servers - Array of MCP server names
|
||||
@@ -577,6 +521,61 @@ function generateHooksSection(hooksDir) {
|
||||
return `${TEMPLATES.hooksSection}\n${TEMPLATES.hooksUsage}\n\n${content}`;
|
||||
}
|
||||
|
||||
/**
|
||||
* Generate the workflows section with a table of all agentic workflows
|
||||
*/
|
||||
function generateWorkflowsSection(workflowsDir) {
|
||||
if (!fs.existsSync(workflowsDir)) {
|
||||
console.log(`Workflows directory does not exist: ${workflowsDir}`);
|
||||
return "";
|
||||
}
|
||||
|
||||
// Get all .md workflow files (flat, no subfolders)
|
||||
const workflowFiles = fs.readdirSync(workflowsDir).filter((file) => {
|
||||
return file.endsWith(".md") && file !== ".gitkeep";
|
||||
});
|
||||
|
||||
// Parse each workflow file
|
||||
const workflowEntries = workflowFiles
|
||||
.map((file) => {
|
||||
const filePath = path.join(workflowsDir, file);
|
||||
const metadata = parseWorkflowMetadata(filePath);
|
||||
if (!metadata) return null;
|
||||
|
||||
return {
|
||||
file,
|
||||
name: metadata.name,
|
||||
description: metadata.description,
|
||||
triggers: metadata.triggers,
|
||||
tags: metadata.tags,
|
||||
};
|
||||
})
|
||||
.filter((entry) => entry !== null)
|
||||
.sort((a, b) => a.name.localeCompare(b.name));
|
||||
|
||||
console.log(`Found ${workflowEntries.length} workflow(s)`);
|
||||
|
||||
if (workflowEntries.length === 0) {
|
||||
return "";
|
||||
}
|
||||
|
||||
// Create table header
|
||||
let content =
|
||||
"| Name | Description | Triggers |\n| ---- | ----------- | -------- |\n";
|
||||
|
||||
// Generate table rows for each workflow
|
||||
for (const workflow of workflowEntries) {
|
||||
const link = `../workflows/${workflow.file}`;
|
||||
const triggers = workflow.triggers.length > 0 ? workflow.triggers.join(", ") : "N/A";
|
||||
|
||||
content += `| [${workflow.name}](${link}) | ${formatTableCell(
|
||||
workflow.description
|
||||
)} | ${triggers} |\n`;
|
||||
}
|
||||
|
||||
return `${TEMPLATES.workflowsSection}\n${TEMPLATES.workflowsUsage}\n\n${content}`;
|
||||
}
|
||||
|
||||
/**
|
||||
* Generate the skills section with a table of all skills
|
||||
*/
|
||||
@@ -918,9 +917,9 @@ async function main() {
|
||||
/^##\s/m,
|
||||
"# "
|
||||
);
|
||||
const promptsHeader = TEMPLATES.promptsSection.replace(/^##\s/m, "# ");
|
||||
const agentsHeader = TEMPLATES.agentsSection.replace(/^##\s/m, "# ");
|
||||
const hooksHeader = TEMPLATES.hooksSection.replace(/^##\s/m, "# ");
|
||||
const workflowsHeader = TEMPLATES.workflowsSection.replace(/^##\s/m, "# ");
|
||||
const skillsHeader = TEMPLATES.skillsSection.replace(/^##\s/m, "# ");
|
||||
const pluginsHeader = TEMPLATES.pluginsSection.replace(
|
||||
/^##\s/m,
|
||||
@@ -934,13 +933,6 @@ async function main() {
|
||||
TEMPLATES.instructionsUsage,
|
||||
registryNames
|
||||
);
|
||||
const promptsReadme = buildCategoryReadme(
|
||||
generatePromptsSection,
|
||||
PROMPTS_DIR,
|
||||
promptsHeader,
|
||||
TEMPLATES.promptsUsage,
|
||||
registryNames
|
||||
);
|
||||
// Generate agents README
|
||||
const agentsReadme = buildCategoryReadme(
|
||||
generateAgentsSection,
|
||||
@@ -959,6 +951,15 @@ async function main() {
|
||||
registryNames
|
||||
);
|
||||
|
||||
// Generate workflows README
|
||||
const workflowsReadme = buildCategoryReadme(
|
||||
generateWorkflowsSection,
|
||||
WORKFLOWS_DIR,
|
||||
workflowsHeader,
|
||||
TEMPLATES.workflowsUsage,
|
||||
registryNames
|
||||
);
|
||||
|
||||
// Generate skills README
|
||||
const skillsReadme = buildCategoryReadme(
|
||||
generateSkillsSection,
|
||||
@@ -987,9 +988,9 @@ async function main() {
|
||||
path.join(DOCS_DIR, "README.instructions.md"),
|
||||
instructionsReadme
|
||||
);
|
||||
writeFileIfChanged(path.join(DOCS_DIR, "README.prompts.md"), promptsReadme);
|
||||
writeFileIfChanged(path.join(DOCS_DIR, "README.agents.md"), agentsReadme);
|
||||
writeFileIfChanged(path.join(DOCS_DIR, "README.hooks.md"), hooksReadme);
|
||||
writeFileIfChanged(path.join(DOCS_DIR, "README.workflows.md"), workflowsReadme);
|
||||
writeFileIfChanged(path.join(DOCS_DIR, "README.skills.md"), skillsReadme);
|
||||
writeFileIfChanged(
|
||||
path.join(DOCS_DIR, "README.plugins.md"),
|
||||
|
||||
@@ -68,7 +68,6 @@ function validateSpecPaths(plugin) {
|
||||
const errors = [];
|
||||
const specs = {
|
||||
agents: { prefix: "./agents/", suffix: ".md", repoDir: "agents", repoSuffix: ".agent.md" },
|
||||
commands: { prefix: "./commands/", suffix: ".md", repoDir: "prompts", repoSuffix: ".prompt.md" },
|
||||
skills: { prefix: "./skills/", suffix: "/", repoDir: "skills", repoFile: "SKILL.md" },
|
||||
};
|
||||
|
||||
|
||||
@@ -253,6 +253,49 @@ function parseHookMetadata(hookPath) {
|
||||
);
|
||||
}
|
||||
|
||||
/**
|
||||
* Parse workflow metadata from a standalone .md workflow file
|
||||
* @param {string} filePath - Path to the workflow .md file
|
||||
* @returns {object|null} Workflow metadata or null on error
|
||||
*/
|
||||
function parseWorkflowMetadata(filePath) {
|
||||
return safeFileOperation(
|
||||
() => {
|
||||
if (!fs.existsSync(filePath)) {
|
||||
return null;
|
||||
}
|
||||
|
||||
const frontmatter = parseFrontmatter(filePath);
|
||||
|
||||
// Validate required fields
|
||||
if (!frontmatter?.name || !frontmatter?.description) {
|
||||
console.warn(
|
||||
`Invalid workflow at ${filePath}: missing name or description in frontmatter`
|
||||
);
|
||||
return null;
|
||||
}
|
||||
|
||||
// Extract triggers from the 'on' field (top-level keys)
|
||||
const onField = frontmatter.on;
|
||||
const triggers = [];
|
||||
if (onField && typeof onField === "object") {
|
||||
triggers.push(...Object.keys(onField));
|
||||
} else if (typeof onField === "string") {
|
||||
triggers.push(onField);
|
||||
}
|
||||
|
||||
return {
|
||||
name: frontmatter.name,
|
||||
description: frontmatter.description,
|
||||
triggers,
|
||||
path: filePath,
|
||||
};
|
||||
},
|
||||
filePath,
|
||||
null
|
||||
);
|
||||
}
|
||||
|
||||
/**
|
||||
* Parse a generic YAML file (used for tools.yml and other config files)
|
||||
* @param {string} filePath - Path to the YAML file
|
||||
@@ -276,6 +319,7 @@ export {
|
||||
parseFrontmatter,
|
||||
parseSkillMetadata,
|
||||
parseHookMetadata,
|
||||
parseWorkflowMetadata,
|
||||
parseYamlFile,
|
||||
safeFileOperation,
|
||||
};
|
||||
|
||||
106
instructions/context7.instructions.md
Normal file
106
instructions/context7.instructions.md
Normal file
@@ -0,0 +1,106 @@
|
||||
---
|
||||
description: 'Use Context7 for authoritative external docs and API references when local context is insufficient'
|
||||
applyTo: '**'
|
||||
---
|
||||
|
||||
# Context7-aware development
|
||||
|
||||
Use Context7 proactively whenever the task depends on **authoritative, current, version-specific external documentation** that is not present in the workspace context.
|
||||
|
||||
This instruction exists so you **do not require the user to type** “use context7” to get up-to-date docs.
|
||||
|
||||
## When to use Context7
|
||||
|
||||
Use Context7 before making decisions or writing code when you need any of the following:
|
||||
|
||||
- **Framework/library API details** (method signatures, configuration keys, expected behaviors).
|
||||
- **Version-sensitive guidance** (breaking changes, deprecations, new defaults).
|
||||
- **Correctness or security-critical patterns** (auth flows, crypto usage, deserialization rules).
|
||||
- **Interpreting unfamiliar error messages** that likely come from third-party tools.
|
||||
- **Best-practice implementation constraints** (rate limits, quotas, required headers, supported formats).
|
||||
|
||||
Also use Context7 when:
|
||||
|
||||
- The user references **a specific framework/library version** (e.g., “Next.js 15”, “React 19”, “AWS SDK v3”).
|
||||
- You’re about to recommend **non-trivial configuration** (CLI flags, config files, auth flows).
|
||||
- You’re unsure whether an API exists, changed names, or got deprecated.
|
||||
|
||||
Skip Context7 for:
|
||||
|
||||
- Purely local refactors, formatting, naming, or logic that is fully derivable from the repo.
|
||||
- Language fundamentals (no external APIs involved).
|
||||
|
||||
## What to fetch
|
||||
|
||||
When using Context7, prefer **primary sources** and narrow queries:
|
||||
|
||||
- Official docs (vendor/framework documentation)
|
||||
- Reference/API pages
|
||||
- Release notes / migration guides
|
||||
- Security advisories (when relevant)
|
||||
|
||||
Gather only what you need to proceed. If multiple candidates exist, pick the most authoritative/current.
|
||||
|
||||
Prefer fetching:
|
||||
|
||||
- The exact method/type/option you will use
|
||||
- The minimal surrounding context needed to avoid misuse (constraints, default behaviors, migration notes)
|
||||
|
||||
## How to incorporate results
|
||||
|
||||
- Translate findings into concrete code/config changes.
|
||||
- **Cite sources** with title + URL when the decision relies on external facts.
|
||||
- If docs conflict or are ambiguous, present the tradeoffs briefly and choose the safest default.
|
||||
|
||||
When the answer requires specific values (flags, config keys, headers), prefer:
|
||||
|
||||
- stating the exact value from docs
|
||||
- calling out defaults and caveats
|
||||
- providing a quick validation step (e.g., “run `--help`”, or a minimal smoke test)
|
||||
|
||||
## How to use Context7 MCP tools (auto)
|
||||
|
||||
When Context7 is available as an MCP server, use it automatically as follows.
|
||||
|
||||
### Tool workflow
|
||||
|
||||
1) **If the user provides a library ID**, use it directly.
|
||||
- Valid forms: `/owner/repo` or `/owner/repo/version` (for pinned versions).
|
||||
|
||||
2) Otherwise, **resolve the library ID** using:
|
||||
- Tool: `resolve-library-id`
|
||||
- Inputs:
|
||||
- `libraryName`: the library/framework name (e.g., “next.js”, “supabase”, “prisma”)
|
||||
- `query`: the user’s task (used to rank matches)
|
||||
|
||||
3) **Fetch relevant documentation** using:
|
||||
- Tool: `query-docs`
|
||||
- Inputs:
|
||||
- `libraryId`: the resolved (or user-supplied) library ID
|
||||
- `query`: the exact task/question you are answering
|
||||
|
||||
4) Only after docs are retrieved: **write the code/steps** based on those docs.
|
||||
|
||||
### Efficiency limits
|
||||
|
||||
- Do **not** call `resolve-library-id` more than **3 times** per user question.
|
||||
- Do **not** call `query-docs` more than **3 times** per user question.
|
||||
- If multiple good matches exist, pick the best one and proceed; ask a clarification question only when the choice materially affects the implementation.
|
||||
|
||||
### Version behavior
|
||||
|
||||
- If the user names a version, reflect it in the library ID when possible (e.g., `/vercel/next.js/v15.1.8`).
|
||||
- If you need reproducibility (CI/builds), prefer pinning to a specific version in examples.
|
||||
|
||||
## Failure handling
|
||||
|
||||
If Context7 cannot find a reliable source:
|
||||
|
||||
1. Say what you tried to verify.
|
||||
2. Proceed with a conservative, well-labeled assumption.
|
||||
3. Suggest a quick validation step (e.g., run a command, check a file, or consult a specific official page).
|
||||
|
||||
## Security & privacy
|
||||
|
||||
- Never request or echo API keys. If configuration requires a key, instruct storing it in environment variables.
|
||||
- Treat retrieved docs as **helpful but not infallible**; for security-sensitive code, prefer official vendor docs and add an explicit verification step.
|
||||
373
instructions/cpp-language-service-tools.instructions.md
Normal file
373
instructions/cpp-language-service-tools.instructions.md
Normal file
@@ -0,0 +1,373 @@
|
||||
---
|
||||
description: You are an expert at using C++ language service tools (GetSymbolReferences_CppTools, GetSymbolInfo_CppTools, GetSymbolCallHierarchy_CppTools). Instructions for calling C++ Tools for Copilot. When working with C++ code, you have access to powerful language service tools that provide accurate, IntelliSense-powered analysis. **Always prefer these tools over manual code inspection, text search, or guessing.**
|
||||
applyTo: "**/*.cpp, **/*.h, **/*.hpp, **/*.cc, **/*.cxx, **/*.c"
|
||||
---
|
||||
|
||||
## Available C++ Tools
|
||||
|
||||
You have access to three specialized C++ tools:
|
||||
|
||||
1. **`GetSymbolInfo_CppTools`** - Find symbol definitions and get type details
|
||||
2. **`GetSymbolReferences_CppTools`** - Find ALL references to a symbol
|
||||
3. **`GetSymbolCallHierarchy_CppTools`** - Analyze function call relationships
|
||||
|
||||
---
|
||||
|
||||
## Mandatory Tool Usage Rules
|
||||
|
||||
### Rule 1: ALWAYS Use GetSymbolReferences_CppTools for Symbol Usages
|
||||
|
||||
**NEVER** rely on manual code inspection, `vscode_listCodeUsages`, `grep_search`, or `read_file` to find where a symbol is used.
|
||||
|
||||
**ALWAYS** call `GetSymbolReferences_CppTools` when:
|
||||
|
||||
- Renaming any symbol (function, variable, class, method, etc.)
|
||||
- Changing function signatures
|
||||
- Refactoring code
|
||||
- Understanding symbol impact
|
||||
- Finding all call sites
|
||||
- Identifying usage patterns
|
||||
- Any task involving "find all uses/usages/references/calls"
|
||||
|
||||
**Why**: `GetSymbolReferences_CppTools` uses C++ IntelliSense and understands:
|
||||
|
||||
- Overloaded functions
|
||||
- Template instantiations
|
||||
- Qualified vs unqualified names
|
||||
- Member function calls
|
||||
- Inherited member usage
|
||||
- Preprocessor-conditional code
|
||||
|
||||
Text search tools will miss these or produce false positives.
|
||||
|
||||
### Rule 2: ALWAYS Use GetSymbolCallHierarchy_CppTools for Function Changes
|
||||
|
||||
Before modifying any function signature, **ALWAYS** call `GetSymbolCallHierarchy_CppTools` with `callsFrom=false` to find all callers.
|
||||
|
||||
**Examples**:
|
||||
|
||||
- Adding/removing function parameters
|
||||
- Changing parameter types
|
||||
- Changing return types
|
||||
- Making functions virtual
|
||||
- Converting to template functions
|
||||
|
||||
**Why**: This ensures you update ALL call sites, not just the ones you can see.
|
||||
|
||||
### Rule 3: ALWAYS Use GetSymbolInfo_CppTools to Understand Symbols
|
||||
|
||||
Before working with unfamiliar code, **ALWAYS** call `GetSymbolInfo_CppTools` to:
|
||||
|
||||
- Find where a symbol is defined
|
||||
- Understand class/struct memory layout
|
||||
- Get type information
|
||||
- Locate declarations
|
||||
|
||||
**NEVER** assume you know what a symbol is without checking.
|
||||
|
||||
---
|
||||
|
||||
## Parameter Usage Guidelines
|
||||
|
||||
### Symbol Names
|
||||
|
||||
- **ALWAYS REQUIRED**: Provide the symbol name
|
||||
- Can be unqualified (`MyFunction`), partially qualified (`MyClass::MyMethod`), or fully qualified (`MyNamespace::MyClass::MyMethod`)
|
||||
- If you have a line number, the symbol should match what appears on that line
|
||||
|
||||
### File Paths
|
||||
|
||||
- **STRONGLY PREFERRED**: Always provide absolute file paths when available
|
||||
- ✅ Good: `C:\Users\Project\src\main.cpp`
|
||||
- ❌ Avoid: `src\main.cpp` (requires resolution, may fail)
|
||||
- If you have access to a file path, include it
|
||||
- If working with user-specified files, use their exact path
|
||||
|
||||
### Line Numbers
|
||||
|
||||
- **CRITICAL**: Line numbers are 1-based, NOT 0-based
|
||||
- **MANDATORY WORKFLOW** when you need a line number:
|
||||
1. First call `read_file` to search for the symbol
|
||||
2. Locate the symbol in the output
|
||||
3. Note the EXACT line number from the output
|
||||
4. VERIFY the line contains the symbol
|
||||
5. Only then call the C++ tool with that line number
|
||||
- **NEVER** guess or estimate line numbers
|
||||
- If you don't have a line number, omit it - the tools will find the symbol
|
||||
|
||||
### Minimal Information Strategy
|
||||
|
||||
Start with minimal information and add more only if needed:
|
||||
|
||||
1. **First attempt**: Symbol name only
|
||||
2. **If ambiguous**: Symbol name + file path
|
||||
3. **If still ambiguous**: Symbol name + file path + line number (after using `read_file`)
|
||||
|
||||
---
|
||||
|
||||
## Common Workflows
|
||||
|
||||
### Renaming a Symbol
|
||||
|
||||
```
|
||||
CORRECT workflow:
|
||||
1. Call GetSymbolReferences_CppTools with symbol name (and file path if available)
|
||||
2. Review ALL references returned
|
||||
3. Update symbol at definition location
|
||||
4. Update symbol at ALL reference locations
|
||||
|
||||
INCORRECT workflow:
|
||||
❌ Using vscode_listCodeUsages or grep_search to find usages
|
||||
❌ Manually inspecting a few files
|
||||
❌ Assuming you know all the usages
|
||||
```
|
||||
|
||||
### Changing a Function Signature
|
||||
|
||||
```
|
||||
CORRECT workflow:
|
||||
1. Call GetSymbolInfo_CppTools to locate the function definition
|
||||
2. Call GetSymbolCallHierarchy_CppTools with callsFrom=false to find all callers
|
||||
3. Call GetSymbolReferences_CppTools to catch any additional references (function pointers, etc.)
|
||||
4. Update function definition
|
||||
5. Update ALL call sites with new signature
|
||||
|
||||
INCORRECT workflow:
|
||||
❌ Changing the function without finding callers
|
||||
❌ Only updating visible call sites
|
||||
❌ Using text search to find calls
|
||||
```
|
||||
|
||||
### Understanding Unfamiliar Code
|
||||
|
||||
```
|
||||
CORRECT workflow:
|
||||
1. Call GetSymbolInfo_CppTools on key types/functions to understand definitions
|
||||
3. Call GetSymbolCallHierarchy_CppTools with callsFrom=true to understand what a function does
|
||||
4. Call GetSymbolCallHierarchy_CppTools with callsFrom=false to understand where a function is used
|
||||
|
||||
INCORRECT workflow:
|
||||
❌ Reading code manually without tool assistance
|
||||
❌ Making assumptions about symbol meanings
|
||||
❌ Skipping hierarchy analysis
|
||||
```
|
||||
|
||||
### Analyzing Function Dependencies
|
||||
|
||||
```
|
||||
CORRECT workflow:
|
||||
1. Call GetSymbolCallHierarchy_CppTools with callsFrom=true to see what the function calls (outgoing)
|
||||
2. Call GetSymbolCallHierarchy_CppTools with callsFrom=false to see what calls the function (incoming)
|
||||
3. Use this to understand code flow and dependencies
|
||||
|
||||
INCORRECT workflow:
|
||||
❌ Manually reading through function body
|
||||
❌ Guessing at call patterns
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Error Handling and Recovery
|
||||
|
||||
### When You Get an Error Message
|
||||
|
||||
**All error messages contain specific recovery instructions. ALWAYS follow them exactly.**
|
||||
|
||||
#### "Symbol name is not valid" Error
|
||||
|
||||
```
|
||||
Error: "The symbol name is not valid: it is either empty or null. Find a valid symbol name. Then call the [tool] tool again"
|
||||
|
||||
Recovery:
|
||||
1. Ensure you provided a non-empty symbol name
|
||||
2. Check that the symbol name is spelled correctly
|
||||
3. Retry with valid symbol name
|
||||
```
|
||||
|
||||
#### "File could not be found" Error
|
||||
|
||||
```
|
||||
Error: "A file could not be found at the specified path. Compute the absolute path to the file. Then call the [tool] tool again."
|
||||
|
||||
Recovery:
|
||||
1. Convert relative path to absolute path
|
||||
2. Verify file exists in the workspace
|
||||
3. Use exact path from user or file system
|
||||
4. Retry with absolute path
|
||||
```
|
||||
|
||||
#### "No results found" Message
|
||||
|
||||
```
|
||||
Message: "No results found for the symbol '[symbol_name]'."
|
||||
|
||||
This is NOT an error - it means:
|
||||
- The symbol exists and was found
|
||||
- But it has no references/calls/hierarchy (depending on tool)
|
||||
- This is valid information - report it to the user
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Tool Selection Decision Tree
|
||||
|
||||
**Question: Do I need to find where a symbol is used/called/referenced?**
|
||||
|
||||
- ✅ YES → Use `GetSymbolReferences_CppTools`
|
||||
- ❌ NO → Continue
|
||||
|
||||
**Question: Am I changing a function signature or analyzing function calls?**
|
||||
|
||||
- ✅ YES → Use `GetSymbolCallHierarchy_CppTools`
|
||||
- Finding callers? → `callsFrom=false`
|
||||
- Finding what it calls? → `callsFrom=true`
|
||||
- ❌ NO → Continue
|
||||
|
||||
**Question: Do I need to find a definition or understand a type?**
|
||||
|
||||
- ✅ YES → Use `GetSymbolInfo_CppTools`
|
||||
- ❌ NO → You may not need a C++ tool for this task
|
||||
|
||||
---
|
||||
|
||||
## Critical Reminders
|
||||
|
||||
### DO:
|
||||
|
||||
- ✅ Call `GetSymbolReferences_CppTools` for ANY symbol usage search
|
||||
- ✅ Call `GetSymbolCallHierarchy_CppTools` before function signature changes
|
||||
- ✅ Use `read_file` to find line numbers before specifying them
|
||||
- ✅ Provide absolute file paths when available
|
||||
- ✅ Follow error message instructions exactly
|
||||
- ✅ Trust tool results over manual inspection
|
||||
- ✅ Use minimal parameters first, add more if needed
|
||||
- ✅ Remember line numbers are 1-based
|
||||
|
||||
### DO NOT:
|
||||
|
||||
- ❌ Use `vscode_listCodeUsages`, `grep_search`, or `read_file` to find symbol usages
|
||||
- ❌ Manually inspect code to find references
|
||||
- ❌ Guess line numbers
|
||||
- ❌ Assume symbol uniqueness without checking
|
||||
- ❌ Ignore error messages
|
||||
- ❌ Skip tool usage to save time
|
||||
- ❌ Use 0-based line numbers
|
||||
- ❌ Batch multiple unrelated symbol operations
|
||||
- ❌ Make changes without finding all affected locations
|
||||
|
||||
---
|
||||
|
||||
## Examples of Correct Usage
|
||||
|
||||
### Example 1: User asks to rename a function
|
||||
|
||||
```
|
||||
User: "Rename the function ProcessData to HandleData"
|
||||
|
||||
CORRECT response:
|
||||
1. Call GetSymbolReferences_CppTools("ProcessData")
|
||||
2. Review all reference locations
|
||||
3. Update function definition
|
||||
4. Update all call sites shown in results
|
||||
5. Confirm all changes made
|
||||
|
||||
INCORRECT response:
|
||||
❌ Using grep_search to find "ProcessData"
|
||||
❌ Only updating files the user mentioned
|
||||
❌ Assuming you found all usages manually
|
||||
```
|
||||
|
||||
### Example 2: User asks to add a parameter to a function
|
||||
|
||||
```
|
||||
User: "Add a parameter 'bool verbose' to the LogMessage function"
|
||||
|
||||
CORRECT response:
|
||||
1. Call GetSymbolInfo_CppTools("LogMessage") to find definition
|
||||
2. Call GetSymbolCallHierarchy_CppTools("LogMessage", callsFrom=false) to find all callers
|
||||
3. Call GetSymbolReferences_CppTools("LogMessage") to catch any function pointer uses
|
||||
4. Update function definition
|
||||
5. Update ALL call sites with new parameter
|
||||
|
||||
INCORRECT response:
|
||||
❌ Only updating the definition
|
||||
❌ Updating only obvious call sites
|
||||
❌ Not using call_hierarchy tool
|
||||
```
|
||||
|
||||
### Example 3: User asks to understand a function
|
||||
|
||||
```
|
||||
User: "What does the Initialize function do?"
|
||||
|
||||
CORRECT response:
|
||||
1. Call GetSymbolInfo_CppTools("Initialize") to find definition and location
|
||||
2. Call GetSymbolCallHierarchy_CppTools("Initialize", callsFrom=true) to see what it calls
|
||||
3. Read the function implementation
|
||||
4. Explain based on code + call hierarchy
|
||||
|
||||
INCORRECT response:
|
||||
❌ Only reading the function body
|
||||
❌ Not checking what it calls
|
||||
❌ Guessing at behavior
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Performance and Best Practices
|
||||
|
||||
### Efficient Tool Usage
|
||||
|
||||
- Call tools in parallel when analyzing multiple independent symbols
|
||||
- Use file paths to speed up symbol resolution
|
||||
- Provide context to narrow searches
|
||||
|
||||
### Iterative Refinement
|
||||
|
||||
- If first tool call is ambiguous, add file path
|
||||
- If still ambiguous, use `read_file` to find exact line
|
||||
- Tools are designed for iteration
|
||||
|
||||
### Understanding Results
|
||||
|
||||
- **Empty results are valid**: "No results found" means the symbol has no references/calls
|
||||
- **Multiple results are common**: C++ has overloading, templates, namespaces
|
||||
- **Trust the tools**: IntelliSense knows C++ semantics better than text search
|
||||
|
||||
---
|
||||
|
||||
## Integration with Other Tools
|
||||
|
||||
### When to use read_file
|
||||
|
||||
- **ONLY** for finding line numbers before calling C++ tools
|
||||
- **ONLY** for reading implementation details after locating symbols
|
||||
- **NEVER** for finding symbol usages (use `GetSymbolReferences_CppTools` instead)
|
||||
|
||||
### When to use vscode_listCodeUsages/grep_search
|
||||
|
||||
- Finding string literals or comments
|
||||
- Searching non-C++ files
|
||||
- Pattern matching in configuration files
|
||||
- **NEVER** for finding C++ symbol usages
|
||||
|
||||
### When to use semantic_search
|
||||
|
||||
- Finding code based on conceptual queries
|
||||
- Locating relevant files in large codebases
|
||||
- Understanding project structure
|
||||
- **Then** use C++ tools for precise symbol analysis
|
||||
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
**The golden rule**: When working with C++ code, think "tool first, manual inspection later."
|
||||
|
||||
1. **Symbol usages?** → `GetSymbolReferences_CppTools`
|
||||
2. **Function calls?** → `GetSymbolCallHierarchy_CppTools`
|
||||
3. **Symbol definition?** → `GetSymbolInfo_CppTools`
|
||||
|
||||
These tools are your primary interface to C++ code understanding. Use them liberally and often. They are fast, accurate, and understand C++ semantics that text search cannot capture.
|
||||
|
||||
**Your success metric**: Did I use the right C++ tool for every symbol-related task?
|
||||
71
instructions/markdown-accessibility.instructions.md
Normal file
71
instructions/markdown-accessibility.instructions.md
Normal file
@@ -0,0 +1,71 @@
|
||||
---
|
||||
description: 'Markdown accessibility guidelines based on GitHub''s 5 best practices for inclusive documentation'
|
||||
applyTo: '**/*.md'
|
||||
---
|
||||
|
||||
# Markdown Accessibility Review Guidelines
|
||||
|
||||
When reviewing markdown files, check for the following accessibility issues based on GitHub's [5 tips for making your GitHub profile page accessible](https://github.blog/developer-skills/github/5-tips-for-making-your-github-profile-page-accessible/). Flag violations and suggest fixes with clear explanations of the accessibility impact.
|
||||
|
||||
## 1. Descriptive Links
|
||||
|
||||
- Flag generic link text such as "click here," "here," "this," "read more," or "link."
|
||||
- Link text must make sense when read out of context, because assistive technology can present links as an isolated list.
|
||||
- Flag multiple links on the same page that share identical text but point to different destinations.
|
||||
- Bare URLs in prose should be converted to descriptive links.
|
||||
|
||||
Bad: `Read my blog post [here](https://example.com)`
|
||||
Good: `Read my blog post "[Crafting an accessible resume](https://example.com)"`
|
||||
|
||||
## 2. Image Alt Text
|
||||
|
||||
- Flag images with empty alt text (e.g., ``) unless they are explicitly decorative.
|
||||
- Flag alt text that is a filename (e.g., `img_1234.jpg`) or generic placeholder (e.g., `screenshot`, `image`).
|
||||
- Alt text should be succinct and descriptive. Include any text visible in the image.
|
||||
- Use "screenshot of" where relevant, but do not prefix with "image of" since screen readers announce that automatically.
|
||||
- For complex images (charts, infographics), suggest summarizing the data in alt text and providing longer descriptions via `<details>` tags or linked content.
|
||||
- When suggesting alt text improvements, present them as recommendations for the author to review. Alt text requires understanding of visual content and context that only the author can properly assess.
|
||||
|
||||
## 3. Heading Hierarchy
|
||||
|
||||
- There must be only one H1 (`#`) per document, used as the page title. Note: in projects where H1 is auto-generated from front matter, start content at H2.
|
||||
- Headings must follow a logical hierarchy and never skip levels (e.g., `##` followed by `####` is a violation).
|
||||
- Flag bold text (`**text**`) used as a visual substitute for a proper heading.
|
||||
- Proper heading structure allows assistive technology users to navigate by section and helps sighted users scan content.
|
||||
|
||||
## 4. Plain Language
|
||||
|
||||
- Flag unnecessarily complex or jargon-heavy language that could be simplified.
|
||||
- Favor short sentences, common words, and active voice.
|
||||
- Flag long, dense paragraphs that could be broken into smaller sections or lists.
|
||||
- When suggesting plain language improvements, present them as recommendations for the author to review. Language decisions require understanding of audience, context, and tone.
|
||||
|
||||
## 5. Lists and Emoji Usage
|
||||
|
||||
### Lists
|
||||
|
||||
- Flag emoji or special characters used as bullet points instead of proper markdown list syntax (`-`, `*`, `+`, or `1.`).
|
||||
- Flag sequential items in plain text that should be structured as a proper list.
|
||||
- Proper list markup allows screen readers to announce list context (e.g., "item 1 of 3").
|
||||
|
||||
### Emoji
|
||||
|
||||
- Flag multiple consecutive emoji, which are disruptive to screen reader users since each emoji name is read aloud in full (e.g., "rocket" "sparkles" "fire").
|
||||
- Flag emoji used to convey meaning that is not also communicated in text.
|
||||
- Emoji should be used sparingly and thoughtfully.
|
||||
|
||||
## Review Priority
|
||||
|
||||
When multiple issues exist, prioritize in this order:
|
||||
|
||||
1. Missing or empty alt text on images
|
||||
2. Skipped heading levels or heading hierarchy issues
|
||||
3. Non-descriptive link text
|
||||
4. Emoji used as bullet points or list markers
|
||||
5. Plain language improvements
|
||||
|
||||
## Review Tone
|
||||
|
||||
- Explain the accessibility impact of each issue, specifying which users are affected (e.g., screen reader users, people with cognitive disabilities, non-native speakers).
|
||||
- Do not remove personality or voice from the writing. Accessibility and engaging content are not mutually exclusive.
|
||||
- Keep suggestions actionable and specific.
|
||||
57
instructions/moodle.instructions.md
Normal file
57
instructions/moodle.instructions.md
Normal file
@@ -0,0 +1,57 @@
|
||||
---
|
||||
applyTo: '**/*.php, **/*.js, **/*.mustache, **/*.xml, **/*.css, **/*.scss'
|
||||
description: 'Instructions for GitHub Copilot to generate code in a Moodle project context.'
|
||||
---
|
||||
|
||||
# Project Context
|
||||
|
||||
This repository contains a Moodle project. Ensure that any generated code is compatible with the specific Moodle version used in this project (for example, Moodle 3.11, 4.1 LTS, or later).
|
||||
|
||||
It includes:
|
||||
- Plugin development (local, block, mod, auth, enrol, tool, etc.)
|
||||
- Theme customization
|
||||
- CLI scripts
|
||||
- Integrations with external services using the Moodle API
|
||||
|
||||
# Code Standards
|
||||
|
||||
- Follow the official Moodle Coding guidelines: https://moodledev.io/general/development/policies/codingstyle
|
||||
- PHP must be compatible with the core version (e.g., PHP 7.4 / 8.0 / 8.1).
|
||||
- Do not use modern syntax that is not supported by core if it breaks compatibility.
|
||||
- Class naming must use Moodle namespaces.
|
||||
- Follow Moodle’s standard plugin directory layout (for example: classes/output, classes/form, db/, lang/, templates/…).
|
||||
- Mandatory use of Moodle security functions:
|
||||
- `$DB` with SQL placeholders
|
||||
- `require_login()`, `require_capability()`
|
||||
- Parameters handled with `required_param()` / `optional_param()`
|
||||
|
||||
# Code Generation Rules
|
||||
|
||||
- When creating new PHP classes in plugins, use the Moodle component (Frankenstyle) namespace that matches the plugin's component name, e.g. `local_myplugin`, `mod_forum`, `block_mycatalog`, `tool_mytool`.
|
||||
- In plugins, always respect the structure:
|
||||
- /db
|
||||
- /lang
|
||||
- /classes
|
||||
- /templates
|
||||
- /version.php
|
||||
- /settings.php
|
||||
- /lib.php (only if necessary)
|
||||
|
||||
- Use renderers and Mustache templates for HTML. Do not mix HTML inside PHP.
|
||||
- In JavaScript code, use AMD modules, not inline scripts.
|
||||
- Prefer Moodle API functions over manual code whenever possible.
|
||||
- Do not invent Moodle functions that do not exist.
|
||||
|
||||
# Examples of What Copilot Should Be Able to Answer
|
||||
|
||||
- "Generate a basic local plugin with version.php, settings.php, and lib.php."
|
||||
- "Create a new table in db/install.xml and an upgrade script in db/upgrade.php."
|
||||
- "Generate a Moodle form using moodleform."
|
||||
- "Create a renderer with Mustache to display a table."
|
||||
|
||||
# Expected Style
|
||||
|
||||
- Clear and specific answers in the Moodle context.
|
||||
- Always include files with full paths.
|
||||
- If there are multiple ways to do something, use the approach recommended by Moodle.
|
||||
|
||||
@@ -15,6 +15,7 @@
|
||||
"plugin:create": "node ./eng/create-plugin.mjs",
|
||||
"skill:validate": "node ./eng/validate-skills.mjs",
|
||||
"skill:create": "node ./eng/create-skill.mjs",
|
||||
"plugin:clean": "node ./eng/clean-materialized-plugins.mjs",
|
||||
"plugin:generate-marketplace": "node ./eng/generate-marketplace.mjs",
|
||||
"website:data": "node ./eng/generate-website-data.mjs",
|
||||
"website:dev": "npm run website:data && npm run --prefix website dev",
|
||||
|
||||
@@ -17,10 +17,10 @@
|
||||
"agents": [
|
||||
"./agents/meta-agentic-project-scaffold.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/suggest-awesome-github-copilot-skills.md",
|
||||
"./commands/suggest-awesome-github-copilot-instructions.md",
|
||||
"./commands/suggest-awesome-github-copilot-prompts.md",
|
||||
"./commands/suggest-awesome-github-copilot-agents.md"
|
||||
"skills": [
|
||||
"./skills/suggest-awesome-github-copilot-skills/",
|
||||
"./skills/suggest-awesome-github-copilot-instructions/",
|
||||
"./skills/suggest-awesome-github-copilot-prompts/",
|
||||
"./skills/suggest-awesome-github-copilot-agents/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -26,8 +26,8 @@
|
||||
"./agents/terraform-azure-planning.md",
|
||||
"./agents/terraform-azure-implement.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/azure-resource-health-diagnose.md",
|
||||
"./commands/az-cost-optimize.md"
|
||||
"skills": [
|
||||
"./skills/azure-resource-health-diagnose/",
|
||||
"./skills/az-cost-optimize/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -15,7 +15,7 @@
|
||||
"agents": [
|
||||
"./agents/clojure-interactive-programming.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/remember-interactive-programming.md"
|
||||
"skills": [
|
||||
"./skills/remember-interactive-programming/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -17,9 +17,9 @@
|
||||
"agents": [
|
||||
"./agents/context-architect.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/context-map.md",
|
||||
"./commands/what-context-needed.md",
|
||||
"./commands/refactor-plan.md"
|
||||
"skills": [
|
||||
"./skills/context-map/",
|
||||
"./skills/what-context-needed/",
|
||||
"./skills/refactor-plan/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -16,14 +16,14 @@
|
||||
"agents": [
|
||||
"./agents/expert-dotnet-software-engineer.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/csharp-async.md",
|
||||
"./commands/aspnet-minimal-api-openapi.md",
|
||||
"./commands/csharp-xunit.md",
|
||||
"./commands/csharp-nunit.md",
|
||||
"./commands/csharp-mstest.md",
|
||||
"./commands/csharp-tunit.md",
|
||||
"./commands/dotnet-best-practices.md",
|
||||
"./commands/dotnet-upgrade.md"
|
||||
"skills": [
|
||||
"./skills/csharp-async/",
|
||||
"./skills/aspnet-minimal-api-openapi/",
|
||||
"./skills/csharp-xunit/",
|
||||
"./skills/csharp-nunit/",
|
||||
"./skills/csharp-mstest/",
|
||||
"./skills/csharp-tunit/",
|
||||
"./skills/dotnet-best-practices/",
|
||||
"./skills/dotnet-upgrade/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -17,7 +17,7 @@
|
||||
"agents": [
|
||||
"./agents/csharp-mcp-expert.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/csharp-mcp-server-generator.md"
|
||||
"skills": [
|
||||
"./skills/csharp-mcp-server-generator/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -21,10 +21,10 @@
|
||||
"./agents/postgresql-dba.md",
|
||||
"./agents/ms-sql-dba.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/sql-optimization.md",
|
||||
"./commands/sql-code-review.md",
|
||||
"./commands/postgresql-optimization.md",
|
||||
"./commands/postgresql-code-review.md"
|
||||
"skills": [
|
||||
"./skills/sql-optimization/",
|
||||
"./skills/sql-code-review/",
|
||||
"./skills/postgresql-optimization/",
|
||||
"./skills/postgresql-code-review/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -13,10 +13,10 @@
|
||||
"integration",
|
||||
"sdk"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/dataverse-python-quickstart.md",
|
||||
"./commands/dataverse-python-advanced-patterns.md",
|
||||
"./commands/dataverse-python-production-code.md",
|
||||
"./commands/dataverse-python-usecase-builder.md"
|
||||
"skills": [
|
||||
"./skills/dataverse-python-quickstart/",
|
||||
"./skills/dataverse-python-advanced-patterns/",
|
||||
"./skills/dataverse-python-production-code/",
|
||||
"./skills/dataverse-python-usecase-builder/"
|
||||
]
|
||||
}
|
||||
|
||||
17
plugins/dataverse/.github/plugin/plugin.json
vendored
Normal file
17
plugins/dataverse/.github/plugin/plugin.json
vendored
Normal file
@@ -0,0 +1,17 @@
|
||||
{
|
||||
"name": "dataverse",
|
||||
"description": "Comprehensive collection for Microsoft Dataverse integrations. Includes MCP setup commands.",
|
||||
"version": "1.0.0",
|
||||
"author": {
|
||||
"name": "Awesome Copilot Community"
|
||||
},
|
||||
"repository": "https://github.com/github/awesome-copilot",
|
||||
"license": "MIT",
|
||||
"keywords": [
|
||||
"dataverse",
|
||||
"mcp"
|
||||
],
|
||||
"skills": [
|
||||
"./skills/mcp-configure/"
|
||||
]
|
||||
}
|
||||
26
plugins/dataverse/README.md
Normal file
26
plugins/dataverse/README.md
Normal file
@@ -0,0 +1,26 @@
|
||||
# Dataverse MCP
|
||||
|
||||
Comprehensive collection for Microsoft Dataverse integrations. Includes MCP setup commands that guide you through configuring Dataverse MCP servers for GitHub Copilot.
|
||||
|
||||
## Installation
|
||||
|
||||
```bash
|
||||
# Using Copilot CLI
|
||||
copilot plugin install dataverse@awesome-copilot
|
||||
```
|
||||
|
||||
## What's Included
|
||||
|
||||
### Skills
|
||||
|
||||
| Skill | Description |
|
||||
|-------|-------------|
|
||||
| `/dataverse:mcp-configure` | Configure Dataverse MCP server for GitHub Copilot with global or project-scoped settings.. |
|
||||
|
||||
## Source
|
||||
|
||||
This plugin is part of [Awesome Copilot](https://github.com/github/awesome-copilot), a community-driven collection of GitHub Copilot extensions.
|
||||
|
||||
## License
|
||||
|
||||
MIT
|
||||
@@ -16,8 +16,8 @@
|
||||
"agents": [
|
||||
"./agents/azure-principal-architect.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/azure-resource-health-diagnose.md",
|
||||
"./commands/multi-stage-dockerfile.md"
|
||||
"skills": [
|
||||
"./skills/azure-resource-health-diagnose/",
|
||||
"./skills/multi-stage-dockerfile/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -22,8 +22,8 @@
|
||||
"./agents/expert-react-frontend-engineer.md",
|
||||
"./agents/electron-angular-native.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/playwright-explore-website.md",
|
||||
"./commands/playwright-generate-test.md"
|
||||
"skills": [
|
||||
"./skills/playwright-explore-website/",
|
||||
"./skills/playwright-generate-test/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -18,7 +18,7 @@
|
||||
"agents": [
|
||||
"./agents/go-mcp-expert.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/go-mcp-server-generator.md"
|
||||
"skills": [
|
||||
"./skills/go-mcp-server-generator/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -15,10 +15,10 @@
|
||||
"junit",
|
||||
"javadoc"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/java-docs.md",
|
||||
"./commands/java-junit.md",
|
||||
"./commands/java-springboot.md",
|
||||
"./commands/create-spring-boot-java-project.md"
|
||||
"skills": [
|
||||
"./skills/java-docs/",
|
||||
"./skills/java-junit/",
|
||||
"./skills/java-springboot/",
|
||||
"./skills/create-spring-boot-java-project/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -20,7 +20,7 @@
|
||||
"agents": [
|
||||
"./agents/java-mcp-expert.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/java-mcp-server-generator.md"
|
||||
"skills": [
|
||||
"./skills/java-mcp-server-generator/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -18,7 +18,7 @@
|
||||
"agents": [
|
||||
"./agents/kotlin-mcp-expert.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/kotlin-mcp-server-generator.md"
|
||||
"skills": [
|
||||
"./skills/kotlin-mcp-server-generator/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -18,9 +18,9 @@
|
||||
"agents": [
|
||||
"./agents/mcp-m365-agent-expert.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/mcp-create-declarative-agent.md",
|
||||
"./commands/mcp-create-adaptive-cards.md",
|
||||
"./commands/mcp-deploy-manage-agents.md"
|
||||
"skills": [
|
||||
"./skills/mcp-create-declarative-agent/",
|
||||
"./skills/mcp-create-adaptive-cards/",
|
||||
"./skills/mcp-deploy-manage-agents/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -18,7 +18,7 @@
|
||||
"agents": [
|
||||
"./agents/openapi-to-application.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/openapi-to-application-code.md"
|
||||
"skills": [
|
||||
"./skills/openapi-to-application-code/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -17,7 +17,7 @@
|
||||
"agents": [
|
||||
"./agents/openapi-to-application.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/openapi-to-application-code.md"
|
||||
"skills": [
|
||||
"./skills/openapi-to-application-code/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -17,7 +17,7 @@
|
||||
"agents": [
|
||||
"./agents/openapi-to-application.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/openapi-to-application-code.md"
|
||||
"skills": [
|
||||
"./skills/openapi-to-application-code/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -18,7 +18,7 @@
|
||||
"agents": [
|
||||
"./agents/openapi-to-application.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/openapi-to-application-code.md"
|
||||
"skills": [
|
||||
"./skills/openapi-to-application-code/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -17,7 +17,7 @@
|
||||
"agents": [
|
||||
"./agents/openapi-to-application.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/openapi-to-application-code.md"
|
||||
"skills": [
|
||||
"./skills/openapi-to-application-code/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -19,7 +19,7 @@
|
||||
"agents": [
|
||||
"./agents/php-mcp-expert.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/php-mcp-server-generator.md"
|
||||
"skills": [
|
||||
"./skills/php-mcp-server-generator/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -19,7 +19,7 @@
|
||||
"agents": [
|
||||
"./agents/power-platform-expert.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/power-apps-code-app-scaffold.md"
|
||||
"skills": [
|
||||
"./skills/power-apps-code-app-scaffold/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -23,10 +23,10 @@
|
||||
"./agents/power-bi-performance-expert.md",
|
||||
"./agents/power-bi-visualization-expert.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/power-bi-dax-optimization.md",
|
||||
"./commands/power-bi-model-design-review.md",
|
||||
"./commands/power-bi-performance-troubleshooting.md",
|
||||
"./commands/power-bi-report-design-consultation.md"
|
||||
"skills": [
|
||||
"./skills/power-bi-dax-optimization/",
|
||||
"./skills/power-bi-model-design-review/",
|
||||
"./skills/power-bi-performance-troubleshooting/",
|
||||
"./skills/power-bi-report-design-consultation/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -17,8 +17,8 @@
|
||||
"agents": [
|
||||
"./agents/power-platform-mcp-integration-expert.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/power-platform-mcp-connector-suite.md",
|
||||
"./commands/mcp-copilot-studio-server-generator.md"
|
||||
"skills": [
|
||||
"./skills/power-platform-mcp-connector-suite/",
|
||||
"./skills/mcp-copilot-studio-server-generator/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -26,14 +26,14 @@
|
||||
"./agents/implementation-plan.md",
|
||||
"./agents/research-technical-spike.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/breakdown-feature-implementation.md",
|
||||
"./commands/breakdown-feature-prd.md",
|
||||
"./commands/breakdown-epic-arch.md",
|
||||
"./commands/breakdown-epic-pm.md",
|
||||
"./commands/create-implementation-plan.md",
|
||||
"./commands/update-implementation-plan.md",
|
||||
"./commands/create-github-issues-feature-from-implementation-plan.md",
|
||||
"./commands/create-technical-spike.md"
|
||||
"skills": [
|
||||
"./skills/breakdown-feature-implementation/",
|
||||
"./skills/breakdown-feature-prd/",
|
||||
"./skills/breakdown-epic-arch/",
|
||||
"./skills/breakdown-epic-pm/",
|
||||
"./skills/create-implementation-plan/",
|
||||
"./skills/update-implementation-plan/",
|
||||
"./skills/create-github-issues-feature-from-implementation-plan/",
|
||||
"./skills/create-technical-spike/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -17,7 +17,7 @@
|
||||
"agents": [
|
||||
"./agents/python-mcp-expert.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/python-mcp-server-generator.md"
|
||||
"skills": [
|
||||
"./skills/python-mcp-server-generator/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -19,7 +19,7 @@
|
||||
"agents": [
|
||||
"./agents/ruby-mcp-expert.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/ruby-mcp-server-generator.md"
|
||||
"skills": [
|
||||
"./skills/ruby-mcp-server-generator/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -21,7 +21,7 @@
|
||||
"agents": [
|
||||
"./agents/rust-mcp-expert.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/rust-mcp-server-generator.md"
|
||||
"skills": [
|
||||
"./skills/rust-mcp-server-generator/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -17,7 +17,7 @@
|
||||
"optimization",
|
||||
"best-practices"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/ai-prompt-engineering-safety-review.md"
|
||||
"skills": [
|
||||
"./skills/ai-prompt-engineering-safety-review/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -7,9 +7,9 @@
|
||||
},
|
||||
"repository": "https://github.com/github/awesome-copilot",
|
||||
"license": "MIT",
|
||||
"commands": [
|
||||
"./commands/structured-autonomy-generate.md",
|
||||
"./commands/structured-autonomy-implement.md",
|
||||
"./commands/structured-autonomy-plan.md"
|
||||
"skills": [
|
||||
"./skills/structured-autonomy-generate/",
|
||||
"./skills/structured-autonomy-implement/",
|
||||
"./skills/structured-autonomy-plan/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -22,7 +22,7 @@
|
||||
"agents": [
|
||||
"./agents/swift-mcp-expert.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/swift-mcp-server-generator.md"
|
||||
"skills": [
|
||||
"./skills/swift-mcp-server-generator/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -16,7 +16,7 @@
|
||||
"agents": [
|
||||
"./agents/research-technical-spike.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/create-technical-spike.md"
|
||||
"skills": [
|
||||
"./skills/create-technical-spike/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -23,11 +23,11 @@
|
||||
"./agents/tdd-refactor.md",
|
||||
"./agents/playwright-tester.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/playwright-explore-website.md",
|
||||
"./commands/playwright-generate-test.md",
|
||||
"./commands/csharp-nunit.md",
|
||||
"./commands/java-junit.md",
|
||||
"./commands/ai-prompt-engineering-safety-review.md"
|
||||
"skills": [
|
||||
"./skills/playwright-explore-website/",
|
||||
"./skills/playwright-generate-test/",
|
||||
"./skills/csharp-nunit/",
|
||||
"./skills/java-junit/",
|
||||
"./skills/ai-prompt-engineering-safety-review/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -17,7 +17,7 @@
|
||||
"agents": [
|
||||
"./agents/typescript-mcp-expert.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/typescript-mcp-server-generator.md"
|
||||
"skills": [
|
||||
"./skills/typescript-mcp-server-generator/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -15,9 +15,9 @@
|
||||
"agent-development",
|
||||
"microsoft-365"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/typespec-create-agent.md",
|
||||
"./commands/typespec-create-api-plugin.md",
|
||||
"./commands/typespec-api-operations.md"
|
||||
"skills": [
|
||||
"./skills/typespec-create-agent/",
|
||||
"./skills/typespec-create-api-plugin/",
|
||||
"./skills/typespec-api-operations/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
agent: 'agent'
|
||||
name: add-educational-comments
|
||||
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']
|
||||
---
|
||||
|
||||
# Add Educational Comments
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
description: "Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations with extensive frameworks, testing methodologies, and educational content."
|
||||
agent: 'agent'
|
||||
name: ai-prompt-engineering-safety-review
|
||||
description: 'Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations with extensive frameworks, testing methodologies, and educational content.'
|
||||
---
|
||||
|
||||
# AI Prompt Engineering Safety Review & Improvement
|
||||
@@ -227,4 +227,4 @@ Provide your analysis in the following structured format:
|
||||
- **Maintain educational value** in your explanations
|
||||
- **Follow industry best practices** from Microsoft, OpenAI, and Google AI
|
||||
|
||||
Remember: Your goal is to help create prompts that are not only effective but also safe, unbiased, secure, and responsible. Every improvement should enhance both functionality and safety.
|
||||
Remember: Your goal is to help create prompts that are not only effective but also safe, unbiased, secure, and responsible. Every improvement should enhance both functionality and safety.
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
agent: "agent"
|
||||
name: "Apple App Store Reviewer"
|
||||
tools: ["vscode", "execute", "read", "search", "web", "upstash/context7/*", "agent", "todo"]
|
||||
description: "Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons."
|
||||
name: apple-appstore-reviewer
|
||||
description: 'Serves as a reviewer of the codebase with instructions on looking for Apple App Store optimizations or rejection reasons.'
|
||||
---
|
||||
|
||||
# Apple App Store Review Specialist
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
agent: 'agent'
|
||||
name: arch-linux-triage
|
||||
description: 'Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices.'
|
||||
model: 'gpt-4.1'
|
||||
tools: ['search', 'runCommands', 'terminalCommand', 'edit/editFiles']
|
||||
---
|
||||
|
||||
# Arch Linux Triage
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: architecture-blueprint-generator
|
||||
description: 'Comprehensive project architecture blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks and architectural patterns, generates visual diagrams, documents implementation patterns, and provides extensible blueprints for maintaining architectural consistency and guiding new development.'
|
||||
agent: 'agent'
|
||||
---
|
||||
|
||||
# Comprehensive Project Architecture Blueprint Generator
|
||||
@@ -1,6 +1,5 @@
|
||||
---
|
||||
agent: 'agent'
|
||||
tools: ['changes', 'search/codebase', 'edit/editFiles', 'problems']
|
||||
name: aspnet-minimal-api-openapi
|
||||
description: 'Create ASP.NET Minimal API endpoints with proper OpenAPI documentation'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
agent: 'agent'
|
||||
name: az-cost-optimize
|
||||
description: 'Analyze Azure resources used in the app (IaC files and/or resources in a target rg) and optimize costs - creating GitHub issues for identified optimizations.'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
agent: 'agent'
|
||||
name: azure-resource-health-diagnose
|
||||
description: 'Analyze Azure resource health, diagnose issues from logs and telemetry, and create a remediation plan for identified problems.'
|
||||
---
|
||||
|
||||
129
skills/bigquery-pipeline-audit/SKILL.md
Normal file
129
skills/bigquery-pipeline-audit/SKILL.md
Normal file
@@ -0,0 +1,129 @@
|
||||
---
|
||||
name: bigquery-pipeline-audit
|
||||
description: 'Audits Python + BigQuery pipelines for cost safety, idempotency, and production readiness. Returns a structured report with exact patch locations.'
|
||||
---
|
||||
|
||||
# BigQuery Pipeline Audit: Cost, Safety and Production Readiness
|
||||
|
||||
You are a senior data engineer reviewing a Python + BigQuery pipeline script.
|
||||
Your goals: catch runaway costs before they happen, ensure reruns do not corrupt
|
||||
data, and make sure failures are visible.
|
||||
|
||||
Analyze the codebase and respond in the structure below (A to F + Final).
|
||||
Reference exact function names and line locations. Suggest minimal fixes, not
|
||||
rewrites.
|
||||
|
||||
---
|
||||
|
||||
## A) COST EXPOSURE: What will actually get billed?
|
||||
|
||||
Locate every BigQuery job trigger (`client.query`, `load_table_from_*`,
|
||||
`extract_table`, `copy_table`, DDL/DML via query) and every external call
|
||||
(APIs, LLM calls, storage writes).
|
||||
|
||||
For each, answer:
|
||||
- Is this inside a loop, retry block, or async gather?
|
||||
- What is the realistic worst-case call count?
|
||||
- For each `client.query`, is `QueryJobConfig.maximum_bytes_billed` set?
|
||||
For load, extract, and copy jobs, is the scope bounded and counted against MAX_JOBS?
|
||||
- Is the same SQL and params being executed more than once in a single run?
|
||||
Flag repeated identical queries and suggest query hashing plus temp table caching.
|
||||
|
||||
**Flag immediately if:**
|
||||
- Any BQ query runs once per date or once per entity in a loop
|
||||
- Worst-case BQ job count exceeds 20
|
||||
- `maximum_bytes_billed` is missing on any `client.query` call
|
||||
|
||||
---
|
||||
|
||||
## B) DRY RUN AND EXECUTION MODES
|
||||
|
||||
Verify a `--mode` flag exists with at least `dry_run` and `execute` options.
|
||||
|
||||
- `dry_run` must print the plan and estimated scope with zero billed BQ execution
|
||||
(BigQuery dry-run estimation via job config is allowed) and zero external API or LLM calls
|
||||
- `execute` requires explicit confirmation for prod (`--env=prod --confirm`)
|
||||
- Prod must not be the default environment
|
||||
|
||||
If missing, propose a minimal `argparse` patch with safe defaults.
|
||||
|
||||
---
|
||||
|
||||
## C) BACKFILL AND LOOP DESIGN
|
||||
|
||||
**Hard fail if:** the script runs one BQ query per date or per entity in a loop.
|
||||
|
||||
Check that date-range backfills use one of:
|
||||
1. A single set-based query with `GENERATE_DATE_ARRAY`
|
||||
2. A staging table loaded with all dates then one join query
|
||||
3. Explicit chunks with a hard `MAX_CHUNKS` cap
|
||||
|
||||
Also check:
|
||||
- Is the date range bounded by default (suggest 14 days max without `--override`)?
|
||||
- If the script crashes mid-run, is it safe to re-run without double-writing?
|
||||
- For backdated simulations, verify data is read from time-consistent snapshots
|
||||
(`FOR SYSTEM_TIME AS OF`, partitioned as-of tables, or dated snapshot tables).
|
||||
Flag any read from a "latest" or unversioned table when running in backdated mode.
|
||||
|
||||
Suggest a concrete rewrite if the current approach is row-by-row.
|
||||
|
||||
---
|
||||
|
||||
## D) QUERY SAFETY AND SCAN SIZE
|
||||
|
||||
For each query, check:
|
||||
- **Partition filter** is on the raw column, not `DATE(ts)`, `CAST(...)`, or
|
||||
any function that prevents pruning
|
||||
- **No `SELECT *`**: only columns actually used downstream
|
||||
- **Joins will not explode**: verify join keys are unique or appropriately scoped
|
||||
and flag any potential many-to-many
|
||||
- **Expensive operations** (`REGEXP`, `JSON_EXTRACT`, UDFs) only run after
|
||||
partition filtering, not on full table scans
|
||||
|
||||
Provide a specific SQL fix for any query that fails these checks.
|
||||
|
||||
---
|
||||
|
||||
## E) SAFE WRITES AND IDEMPOTENCY
|
||||
|
||||
Identify every write operation. Flag plain `INSERT`/append with no dedup logic.
|
||||
|
||||
Each write should use one of:
|
||||
1. `MERGE` on a deterministic key (e.g., `entity_id + date + model_version`)
|
||||
2. Write to a staging table scoped to the run, then swap or merge into final
|
||||
3. Append-only with a dedupe view:
|
||||
`QUALIFY ROW_NUMBER() OVER (PARTITION BY <key>) = 1`
|
||||
|
||||
Also check:
|
||||
- Will a re-run create duplicate rows?
|
||||
- Is the write disposition (`WRITE_TRUNCATE` vs `WRITE_APPEND`) intentional
|
||||
and documented?
|
||||
- Is `run_id` being used as part of the merge or dedupe key? If so, flag it.
|
||||
`run_id` should be stored as a metadata column, not as part of the uniqueness
|
||||
key, unless you explicitly want multi-run history.
|
||||
|
||||
State the recommended approach and the exact dedup key for this codebase.
|
||||
|
||||
---
|
||||
|
||||
## F) OBSERVABILITY: Can you debug a failure?
|
||||
|
||||
Verify:
|
||||
- Failures raise exceptions and abort with no silent `except: pass` or warn-only
|
||||
- Each BQ job logs: job ID, bytes processed or billed when available,
|
||||
slot milliseconds, and duration
|
||||
- A run summary is logged or written at the end containing:
|
||||
`run_id, env, mode, date_range, tables written, total BQ jobs, total bytes`
|
||||
- `run_id` is present and consistent across all log lines
|
||||
|
||||
If `run_id` is missing, propose a one-line fix:
|
||||
`run_id = run_id or datetime.utcnow().strftime('%Y%m%dT%H%M%S')`
|
||||
|
||||
---
|
||||
|
||||
## Final
|
||||
|
||||
**1. PASS / FAIL** with specific reasons per section (A to F).
|
||||
**2. Patch list** ordered by risk, referencing exact functions to change.
|
||||
**3. If FAIL: Top 3 cost risks** with a rough worst-case estimate
|
||||
(e.g., "loop over 90 dates x 3 retries = 270 BQ jobs").
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
agent: agent
|
||||
name: boost-prompt
|
||||
description: 'Interactive prompt refinement workflow: interrogates scope, deliverables, constraints; copies final markdown to clipboard; never writes code. Requires the Joyride extension.'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
agent: 'agent'
|
||||
name: breakdown-epic-arch
|
||||
description: 'Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
agent: 'agent'
|
||||
name: breakdown-epic-pm
|
||||
description: 'Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
agent: 'agent'
|
||||
name: breakdown-feature-implementation
|
||||
description: 'Prompt for creating detailed feature implementation plans, following Epoch monorepo structure.'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
agent: 'agent'
|
||||
name: breakdown-feature-prd
|
||||
description: 'Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
agent: 'agent'
|
||||
name: breakdown-plan
|
||||
description: 'Issue Planning and Automation prompt that generates comprehensive project plans with Epic > Feature > Story/Enabler > Test hierarchy, dependencies, priorities, and automated tracking.'
|
||||
---
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
agent: 'agent'
|
||||
name: breakdown-test
|
||||
description: 'Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for GitHub projects.'
|
||||
---
|
||||
|
||||
@@ -1,8 +1,6 @@
|
||||
---
|
||||
agent: 'agent'
|
||||
name: centos-linux-triage
|
||||
description: 'Triage and resolve CentOS issues using RHEL-compatible tooling, SELinux-aware practices, and firewalld.'
|
||||
model: 'gpt-4.1'
|
||||
tools: ['search', 'runCommands', 'terminalCommand', 'edit/editFiles']
|
||||
---
|
||||
|
||||
# CentOS Linux Triage
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: code-exemplars-blueprint-generator
|
||||
description: 'Technology-agnostic prompt generator that creates customizable AI prompts for scanning codebases and identifying high-quality code exemplars. Supports multiple programming languages (.NET, Java, JavaScript, TypeScript, React, Angular, Python) with configurable analysis depth, categorization methods, and documentation formats to establish coding standards and maintain consistency across development teams.'
|
||||
agent: 'agent'
|
||||
---
|
||||
|
||||
# Code Exemplars Blueprint Generator
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user