* initial prototype of partners collection with featured collection support * Starting to add the partners * Preparing the repo for how the custom agents will work * moving some files around * Moving a bunch of stuff around to make the file easier to read * improving the front matter parsing by using a real library * Some verbage updates * some more verbage * Fixing spelling mistake * tweaking badges * Updating contributing guide to be correct * updating casing to match product * More agents * Better handling link to mcp registry * links to install mcp servers fixed up * Updating collection tags * writing the mcp registry url out properly * Adding custom agents for C# and WinForms Expert custom agents to improve your experience when working with C# and WinForms in Copilot * Adding to agents readme * Adding PagerDuty agent * Fixing description for terraform agent * Adding custom agents to the README usage * Removing the button to make the links more obvious * docs: relocate category READMEs to /docs and update generation + internal links * Updating prompts for new path * formatting --------- Co-authored-by: Chris Patterson <chrispat@github.com>
4.5 KiB
4.5 KiB
| mode | description | tools | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| agent | 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. |
|
Suggest Awesome GitHub Copilot Prompts
Analyze current repository context and suggest relevant prompt files from the GitHub awesome-copilot repository that are not already available in this repository.
Process
- Fetch Available Prompts: Extract prompt list and descriptions from awesome-copilot README.prompts.md. Must use
#fetchtool. - Scan Local Prompts: Discover existing prompt files in
.github/prompts/folder - Extract Descriptions: Read front matter from local prompt files to get descriptions
- Analyze Context: Review chat history, repository files, and current project needs
- Compare Existing: Check against prompts already available in this repository
- Match Relevance: Compare available prompts against identified patterns and requirements
- Present Options: Display relevant prompts with descriptions, rationale, and availability status
- Validate: Ensure suggested prompts would add value not already covered by existing prompts
- Output: Provide structured table with suggestions, descriptions, and links to both awesome-copilot prompts and similar local prompts AWAIT user request to proceed with installation of specific instructions. DO NOT INSTALL UNLESS DIRECTED TO DO SO.
- Download Assets: For requested instructions, automatically download and install individual instructions to
.github/prompts/folder. Do NOT adjust content of the files. Use#todostool to track progress. Prioritize use of#fetchtool to download assets, but may usecurlusing#runInTerminaltool to ensure all content is retrieved.
Context Analysis Criteria
🔍 Repository Patterns:
- Programming languages used (.cs, .js, .py, etc.)
- Framework indicators (ASP.NET, React, Azure, etc.)
- Project types (web apps, APIs, libraries, tools)
- Documentation needs (README, specs, ADRs)
🗨️ Chat History Context:
- Recent discussions and pain points
- Feature requests or implementation needs
- Code review patterns
- Development workflow requirements
Output Format
Display analysis results in structured table comparing awesome-copilot prompts with existing repository prompts:
| Awesome-Copilot Prompt | Description | Already Installed | Similar Local Prompt | Suggestion Rationale |
|---|---|---|---|---|
| code-review.md | Automated code review prompts | ❌ No | None | Would enhance development workflow with standardized code review processes |
| documentation.md | Generate project documentation | ✅ Yes | create_oo_component_documentation.prompt.md | Already covered by existing documentation prompts |
| debugging.md | Debug assistance prompts | ❌ No | None | Could improve troubleshooting efficiency for development team |
Local Prompts Discovery Process
- List all
*.prompt.mdfiles directory.github/prompts/. - For each discovered file, read front matter to extract
description - Build comprehensive inventory of existing prompts
- Use this inventory to avoid suggesting duplicates
Requirements
- Use
githubRepotool to get content from awesome-copilot repository - Scan local file system for existing prompts in
.github/prompts/directory - Read YAML front matter from local prompt files to extract descriptions
- Compare against existing prompts in this repository to avoid duplicates
- Focus on gaps in current prompt library coverage
- Validate that suggested prompts align with repository's purpose and standards
- Provide clear rationale for each suggestion
- Include links to both awesome-copilot prompts and similar local prompts
- Don't provide any additional information or context beyond the table and the analysis
Icons Reference
- ✅ Already installed in repo
- ❌ Not installed in repo