Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-02-20 02:15:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add outdated detection to collections, instructions, and prompts suggestion files

Browse Source 
Similar to c12041b which added outdated agent detection, this commit adds:
- Version comparison process for detecting outdated local assets
- Fetch remote versions step in the process workflow
- Updated icons reference with outdated status indicators
- Update handling sections for managing outdated assets
- Updated output table examples to show outdated status
This commit is contained in:
Kent Yao
2026-01-15 16:15:00 +08:00
parent 0b9ad6eaaa
commit c4f2978a51
5 changed files with 148 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -1,6 +1,6 @@
---
agent: 'agent'
description: 'Suggest relevant GitHub Copilot collections from the awesome-copilot repository based on current repository context and chat history, providing automatic download and installation of collection assets.'
description: 'Suggest relevant GitHub Copilot collections from the awesome-copilot repository based on current repository context and chat history, providing automatic download and installation of collection assets, and identifying outdated collection assets that need updates.'
tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'web/fetch', 'githubRepo', 'todos', 'search']
---
# Suggest Awesome GitHub Copilot Collections
@@ -12,13 +12,22 @@ Analyze current repository context and suggest relevant collections from the [Gi
1. **Fetch Available Collections**: Extract collection list and descriptions from [awesome-copilot README.collections.md](https://github.com/github/awesome-copilot/blob/main/docs/README.collections.md). Must use `#fetch` tool.
2. **Scan Local Assets**: Discover existing prompt files in `prompts/`, instruction files in `instructions/`, and chat modes in `agents/` folders
3. **Extract Local Descriptions**: Read front matter from local asset files to understand existing capabilities
4. **Analyze Repository Context**: Review chat history, repository files, programming languages, frameworks, and current project needs
5. **Match Collection Relevance**: Compare available collections against identified patterns and requirements
6. **Check Asset Overlap**: For relevant collections, analyze individual items to avoid duplicates with existing repository assets
7. **Present Collection Options**: Display relevant collections with descriptions, item counts, and rationale for suggestion
8. **Provide Usage Guidance**: Explain how the installed collection enhances the development workflow
**AWAIT** user request to proceed with installation of specific collections. DO NOT INSTALL UNLESS DIRECTED TO DO SO.
9. **Download Assets**: For requested collections, automatically download and install each individual asset (prompts, instructions, chat modes) to appropriate directories. Do NOT adjust content of the files. Prioritize use of `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
4. **Fetch Remote Versions**: For each local asset that matches a collection item, fetch the corresponding version from awesome-copilot repository using raw GitHub URLs (e.g., `https://raw.githubusercontent.com/github/awesome-copilot/main/<type>/<filename>`)
5. **Compare Versions**: Compare local asset content with remote versions to identify:
- Assets that are up-to-date (exact match)
- Assets that are outdated (content differs)
- Key differences in outdated assets (tools, description, content)
6. **Analyze Repository Context**: Review chat history, repository files, programming languages, frameworks, and current project needs
7. **Match Collection Relevance**: Compare available collections against identified patterns and requirements
8. **Check Asset Overlap**: For relevant collections, analyze individual items to avoid duplicates with existing repository assets
9. **Present Collection Options**: Display relevant collections with descriptions, item counts, outdated asset counts, and rationale for suggestion
10. **Provide Usage Guidance**: Explain how the installed collection enhances the development workflow
**AWAIT** user request to proceed with installation or updates of specific collections. DO NOT INSTALL OR UPDATE UNLESS DIRECTED TO DO SO.
11. **Download/Update Assets**: For requested collections, automatically:
- Download new assets to appropriate directories
- Update outdated assets by replacing with latest version from awesome-copilot
- Do NOT adjust content of the files
- Use `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved
## Context Analysis Criteria
@@ -55,6 +64,7 @@ For each suggested collection, break down individual assets:
**Azure & Cloud Development Collection Analysis:**
- ✅ **New Assets (12)**: Azure cost optimization prompts, Bicep planning mode, AVM modules, Logic Apps expert mode
- ⚠️ **Similar Assets (3)**: Azure DevOps pipelines (similar to existing CI/CD), Terraform (basic overlap), Containerization (Docker basics covered)
- 🔄 **Outdated Assets (2)**: azure-iac-generator.agent.md (tools updated), bicep-implement.agent.md (description changed)
- 🎯 **High Value**: Cost optimization tools, Infrastructure as Code expertise, Azure-specific architectural guidance
**Installation Preview:**
@@ -86,6 +96,21 @@ For each suggested collection, break down individual assets:
- Industry best practices for identified project types
- Missing expertise areas (security, performance, architecture, etc.)
## Version Comparison Process
1. For each local asset file that corresponds to a collection item, construct the raw GitHub URL:
- Agents: `https://raw.githubusercontent.com/github/awesome-copilot/main/agents/<filename>`
- Prompts: `https://raw.githubusercontent.com/github/awesome-copilot/main/prompts/<filename>`
- Instructions: `https://raw.githubusercontent.com/github/awesome-copilot/main/instructions/<filename>`
2. Fetch the remote version using the `fetch` tool
3. Compare entire file content (including front matter and body)
4. Identify specific differences:
- **Front matter changes** (description, tools, applyTo patterns)
- **Tools array modifications** (added, removed, or renamed tools)
- **Content updates** (instructions, examples, guidelines)
5. Document key differences for outdated assets
6. Calculate similarity to determine if update is needed
## Collection Asset Download Process
When user confirms a collection installation:
@@ -141,9 +166,18 @@ After installing a collection, provide:
## Icons Reference
- ✅ Collection recommended for installation
- ✅ Collection recommended for installation / Asset up-to-date
- ⚠️ Collection has some asset overlap but still valuable
- ❌ Collection not recommended (significant overlap or not relevant)
- 🎯 High-value collection that fills major capability gaps
- 📁 Collection partially installed (some assets skipped due to duplicates)
- 🔄 Collection needs customization for repository-specific needs
- 🔄 Asset outdated (update available from awesome-copilot)
## Update Handling
When outdated collection assets are identified:
1. Include them in the asset analysis with 🔄 status
2. Document specific differences for each outdated asset
3. Provide recommendation to update with key changes noted
4. When user requests update, replace entire local file with remote version
5. Preserve file location in appropriate directory (`agents/`, `prompts/`, or `instructions/`)

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

@@ -1,6 +1,6 @@
---
agent: 'agent'
description: 'Suggest relevant GitHub Copilot instruction files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing instructions in this repository.'
description: 'Suggest relevant GitHub Copilot instruction files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing instructions in this repository, and identifying outdated instructions that need updates.'
tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'web/fetch', 'githubRepo', 'todos', 'search']
---
# Suggest Awesome GitHub Copilot Instructions
@@ -12,14 +12,24 @@ Analyze current repository context and suggest relevant copilot-instruction file
1. **Fetch Available Instructions**: Extract instruction list and descriptions from [awesome-copilot README.instructions.md](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md). Must use `#fetch` tool.
2. **Scan Local Instructions**: Discover existing instruction files in `.github/instructions/` folder
3. **Extract Descriptions**: Read front matter from local instruction files to get descriptions and `applyTo` patterns
4. **Analyze Context**: Review chat history, repository files, and current project needs
5. **Compare Existing**: Check against instructions already available in this repository
6. **Match Relevance**: Compare available instructions against identified patterns and requirements
7. **Present Options**: Display relevant instructions with descriptions, rationale, and availability status
8. **Validate**: Ensure suggested instructions would add value not already covered by existing instructions
9. **Output**: Provide structured table with suggestions, descriptions, and links to both awesome-copilot instructions and similar local instructions
**AWAIT** user request to proceed with installation of specific instructions. DO NOT INSTALL UNLESS DIRECTED TO DO SO.
10. **Download Assets**: For requested instructions, automatically download and install individual instructions to `.github/instructions/` folder. Do NOT adjust content of the files. Use `#todos` tool to track progress. Prioritize use of `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
4. **Fetch Remote Versions**: For each local instruction, fetch the corresponding version from awesome-copilot repository using raw GitHub URLs (e.g., `https://raw.githubusercontent.com/github/awesome-copilot/main/instructions/<filename>`)
5. **Compare Versions**: Compare local instruction content with remote versions to identify:
- Instructions that are up-to-date (exact match)
- Instructions that are outdated (content differs)
- Key differences in outdated instructions (description, applyTo patterns, content)
6. **Analyze Context**: Review chat history, repository files, and current project needs
7. **Compare Existing**: Check against instructions already available in this repository
8. **Match Relevance**: Compare available instructions against identified patterns and requirements
9. **Present Options**: Display relevant instructions with descriptions, rationale, and availability status including outdated instructions
10. **Validate**: Ensure suggested instructions would add value not already covered by existing instructions
11. **Output**: Provide structured table with suggestions, descriptions, and links to both awesome-copilot instructions and similar local instructions
**AWAIT** user request to proceed with installation or updates of specific instructions. DO NOT INSTALL OR UPDATE UNLESS DIRECTED TO DO SO.
12. **Download/Update Assets**: For requested instructions, automatically:
- Download new instructions to `.github/instructions/` folder
- Update outdated instructions by replacing with latest version from awesome-copilot
- Do NOT adjust content of the files
- Use `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved
- Use `#todos` tool to track progress
## Context Analysis Criteria
@@ -41,9 +51,9 @@ Display analysis results in structured table comparing awesome-copilot instructi
| Awesome-Copilot Instruction | Description | Already Installed | Similar Local Instruction | Suggestion Rationale |
|------------------------------|-------------|-------------------|---------------------------|---------------------|
| [blazor.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/blazor.instructions.md) | Blazor development guidelines | ❌ No | blazor.instructions.md | Already covered by existing Blazor instructions |
| [blazor.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/blazor.instructions.md) | Blazor development guidelines | ✅ Yes | blazor.instructions.md | Already covered by existing Blazor instructions |
| [reactjs.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/reactjs.instructions.md) | ReactJS development standards | ❌ No | None | Would enhance React development with established patterns |
| [java.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/java.instructions.md) | Java development best practices | ❌ No | None | Could improve Java code quality and consistency |
| [java.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/java.instructions.md) | Java development best practices | ⚠️ Outdated | java.instructions.md | applyTo pattern differs: remote uses `'**/*.java'` vs local `'*.java'` - Update recommended |
## Local Instructions Discovery Process
@@ -52,6 +62,18 @@ Display analysis results in structured table comparing awesome-copilot instructi
3. Build comprehensive inventory of existing instructions with their applicable file patterns
4. Use this inventory to avoid suggesting duplicates
## Version Comparison Process
1. For each local instruction file, construct the raw GitHub URL to fetch the remote version:
- Pattern: `https://raw.githubusercontent.com/github/awesome-copilot/main/instructions/<filename>`
2. Fetch the remote version using the `fetch` tool
3. Compare entire file content (including front matter and body)
4. Identify specific differences:
- **Front matter changes** (description, applyTo patterns)
- **Content updates** (guidelines, examples, best practices)
5. Document key differences for outdated instructions
6. Calculate similarity to determine if update is needed
## File Structure Requirements
Based on GitHub documentation, copilot-instructions files should be:
@@ -71,18 +93,30 @@ applyTo: '**/*.js,**/*.ts' # Optional: glob patterns for file matching
## Requirements
- Use `githubRepo` tool to get content from awesome-copilot repository
- Scan local file system for existing instructions in `instructions/` directory
- Use `githubRepo` tool to get content from awesome-copilot repository instructions folder
- Scan local file system for existing instructions in `.github/instructions/` directory
- Read YAML front matter from local instruction files to extract descriptions and `applyTo` patterns
- Compare local instructions with remote versions to detect outdated instructions
- Compare against existing instructions in this repository to avoid duplicates
- Focus on gaps in current instruction library coverage
- Validate that suggested instructions align with repository's purpose and standards
- Provide clear rationale for each suggestion
- Include links to both awesome-copilot instructions and similar local instructions
- Clearly identify outdated instructions with specific differences noted
- Consider technology stack compatibility and project-specific needs
- Don't provide any additional information or context beyond the table and the analysis
## Icons Reference
- ✅ Already installed in repo
- ✅ Already installed and up-to-date
- ⚠️ Installed but outdated (update available)
- ❌ Not installed in repo
## Update Handling
When outdated instructions are identified:
1. Include them in the output table with ⚠️ status
2. Document specific differences in the "Suggestion Rationale" column
3. Provide recommendation to update with key changes noted
4. When user requests update, replace entire local file with remote version
5. Preserve file location in `.github/instructions/` directory

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

@@ -1,6 +1,6 @@
---
agent: 'agent'
description: 'Suggest relevant GitHub Copilot prompt files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing prompts in this repository.'
description: 'Suggest relevant GitHub Copilot prompt files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing prompts in this repository, and identifying outdated prompts that need updates.'
tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'web/fetch', 'githubRepo', 'todos', 'search']
---
# Suggest Awesome GitHub Copilot Prompts
@@ -12,14 +12,24 @@ Analyze current repository context and suggest relevant prompt files from the [G
1. **Fetch Available Prompts**: Extract prompt list and descriptions from [awesome-copilot README.prompts.md](https://github.com/github/awesome-copilot/blob/main/docs/README.prompts.md). Must use `#fetch` tool.
2. **Scan Local Prompts**: Discover existing prompt files in `.github/prompts/` folder
3. **Extract Descriptions**: Read front matter from local prompt files to get descriptions
4. **Analyze Context**: Review chat history, repository files, and current project needs
5. **Compare Existing**: Check against prompts already available in this repository
6. **Match Relevance**: Compare available prompts against identified patterns and requirements
7. **Present Options**: Display relevant prompts with descriptions, rationale, and availability status
8. **Validate**: Ensure suggested prompts would add value not already covered by existing prompts
9. **Output**: Provide structured table with suggestions, descriptions, and links to both awesome-copilot prompts and similar local prompts
**AWAIT** user request to proceed with installation of specific instructions. DO NOT INSTALL UNLESS DIRECTED TO DO SO.
10. **Download Assets**: For requested instructions, automatically download and install individual instructions to `.github/prompts/` folder. Do NOT adjust content of the files. Use `#todos` tool to track progress. Prioritize use of `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved.
4. **Fetch Remote Versions**: For each local prompt, fetch the corresponding version from awesome-copilot repository using raw GitHub URLs (e.g., `https://raw.githubusercontent.com/github/awesome-copilot/main/prompts/<filename>`)
5. **Compare Versions**: Compare local prompt content with remote versions to identify:
- Prompts that are up-to-date (exact match)
- Prompts that are outdated (content differs)
- Key differences in outdated prompts (tools, description, content)
6. **Analyze Context**: Review chat history, repository files, and current project needs
7. **Compare Existing**: Check against prompts already available in this repository
8. **Match Relevance**: Compare available prompts against identified patterns and requirements
9. **Present Options**: Display relevant prompts with descriptions, rationale, and availability status including outdated prompts
10. **Validate**: Ensure suggested prompts would add value not already covered by existing prompts
11. **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 or updates of specific prompts. DO NOT INSTALL OR UPDATE UNLESS DIRECTED TO DO SO.
12. **Download/Update Assets**: For requested prompts, automatically:
- Download new prompts to `.github/prompts/` folder
- Update outdated prompts by replacing with latest version from awesome-copilot
- Do NOT adjust content of the files
- Use `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved
- Use `#todos` tool to track progress
## Context Analysis Criteria
@@ -41,31 +51,56 @@ Display analysis results in structured table comparing awesome-copilot prompts w
| Awesome-Copilot Prompt | Description | Already Installed | Similar Local Prompt | Suggestion Rationale |
|-------------------------|-------------|-------------------|---------------------|---------------------|
| [code-review.md](https://github.com/github/awesome-copilot/blob/main/prompts/code-review.md) | Automated code review prompts | ❌ No | None | Would enhance development workflow with standardized code review processes |
| [documentation.md](https://github.com/github/awesome-copilot/blob/main/prompts/documentation.md) | Generate project documentation | ✅ Yes | create_oo_component_documentation.prompt.md | Already covered by existing documentation prompts |
| [debugging.md](https://github.com/github/awesome-copilot/blob/main/prompts/debugging.md) | Debug assistance prompts | ❌ No | None | Could improve troubleshooting efficiency for development team |
| [code-review.prompt.md](https://github.com/github/awesome-copilot/blob/main/prompts/code-review.prompt.md) | Automated code review prompts | ❌ No | None | Would enhance development workflow with standardized code review processes |
| [documentation.prompt.md](https://github.com/github/awesome-copilot/blob/main/prompts/documentation.prompt.md) | Generate project documentation | ✅ Yes | create_oo_component_documentation.prompt.md | Already covered by existing documentation prompts |
| [debugging.prompt.md](https://github.com/github/awesome-copilot/blob/main/prompts/debugging.prompt.md) | Debug assistance prompts | ⚠️ Outdated | debugging.prompt.md | Tools configuration differs: remote uses `'codebase'` vs local missing - Update recommended |
## Local Prompts Discovery Process
1. List all `*.prompt.md` files directory `.github/prompts/`.
1. List all `*.prompt.md` files in `.github/prompts/` directory
2. For each discovered file, read front matter to extract `description`
3. Build comprehensive inventory of existing prompts
4. Use this inventory to avoid suggesting duplicates
## Version Comparison Process
1. For each local prompt file, construct the raw GitHub URL to fetch the remote version:
- Pattern: `https://raw.githubusercontent.com/github/awesome-copilot/main/prompts/<filename>`
2. Fetch the remote version using the `fetch` tool
3. Compare entire file content (including front matter and body)
4. Identify specific differences:
- **Front matter changes** (description, tools, mode)
- **Tools array modifications** (added, removed, or renamed tools)
- **Content updates** (instructions, examples, guidelines)
5. Document key differences for outdated prompts
6. Calculate similarity to determine if update is needed
## Requirements
- Use `githubRepo` tool to get content from awesome-copilot repository
- Use `githubRepo` tool to get content from awesome-copilot repository prompts folder
- Scan local file system for existing prompts in `.github/prompts/` directory
- Read YAML front matter from local prompt files to extract descriptions
- Compare local prompts with remote versions to detect outdated prompts
- 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
- Clearly identify outdated prompts with specific differences noted
- Don't provide any additional information or context beyond the table and the analysis
## Icons Reference
- ✅ Already installed in repo
- ✅ Already installed and up-to-date
- ⚠️ Installed but outdated (update available)
- ❌ Not installed in repo
## Update Handling
When outdated prompts are identified:
1. Include them in the output table with ⚠️ status
2. Document specific differences in the "Suggestion Rationale" column
3. Provide recommendation to update with key changes noted
4. When user requests update, replace entire local file with remote version
5. Preserve file location in `.github/prompts/` directory