Suggest Awesome Github Copilot Instructions

Context Analysis Criteria

🔍 Repository Patterns:

• Programming languages used (.cs, .js, .py, .ts, etc.)
• Framework indicators (ASP.NET, React, Azure, Next.js, etc.)
• Project types (web apps, APIs, libraries, tools)
• Development workflow requirements (testing, CI/CD, deployment)

🗨️ Chat History Context:

• Recent discussions and pain points
• Technology-specific questions
• Coding standards discussions
• Development workflow requirements

Output Format

Display analysis results in structured table comparing awesome-copilot instructions with existing repository instructions:

Local Instructions Discovery Process

1. List all *.instructions.md files in the instructions/ directory
2. For each discovered file, read front matter to extract description and applyTo patterns
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:

• Repository-wide instructions: .github/copilot-instructions.md (applies to entire repository)
• Path-specific instructions: .github/instructions/NAME.instructions.md (applies to specific file patterns via applyTo frontmatter)
• Community instructions: instructions/NAME.instructions.md (for sharing and distribution)

Front Matter Structure

Instructions files in awesome-copilot use this front matter format:

---