Prompt file imported from lewismorgan/lewis (.github/prompts/suggest-awesome-github-copilot-instructions.prompt.md). Copyright stays with the author.

Suggest Awesome GitHub Copilot Instructions

Name: suggest-awesome-github-copilot-instructions
Author: lewismorgan

Analyze current repository context and suggest relevant copilot-instruction files from the GitHub awesome-copilot repository that are not already available in this repository.

Process

Fetch Available Instructions: Extract instruction list and descriptions from awesome-copilot README.instructions.md. Must use #fetch tool.
Scan Local Instructions: Discover existing instruction files in .github/instructions/ folder
Extract Descriptions: Read front matter from local instruction files to get descriptions and applyTo patterns
Analyze Context: Review chat history, repository files, and current project needs
Compare Existing: Check against instructions already available in this repository
Match Relevance: Compare available instructions against identified patterns and requirements
Present Options: Display relevant instructions with descriptions, rationale, and availability status
Validate: Ensure suggested instructions would add value not already covered by existing instructions
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.
Download Assets: For requested instructions, automatically download and install individual instructions to .github/instructions/ folder. Do NOT adjust content of the files. Use #todos tool to track progress. Prioritize use of #fetch tool to download assets, but may use curl using #runInTerminal tool to ensure all content is retrieved.

Context Analysis Criteria

🔍 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:

Awesome-Copilot Instruction	Description	Already Installed	Similar Local Instruction	Suggestion Rationale
blazor.instructions.md	Blazor development guidelines	❌ No	blazor.instructions.md	Already covered by existing Blazor instructions
reactjs.instructions.md	ReactJS development standards	❌ No	None	Would enhance React development with established patterns
java.instructions.md	Java development best practices	❌ No	None	Could improve Java code quality and consistency

Local Instructions Discovery Process

List all *.instructions.md files in the instructions/ directory
For each discovered file, read front matter to extract description and applyTo patterns
Build comprehensive inventory of existing instructions with their applicable file patterns
Use this inventory to avoid suggesting duplicates

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:

---
description: 'Brief description of what this instruction provides'
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
Read YAML front matter from local instruction files to extract descriptions and applyTo patterns
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
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
❌ Not installed in repo

# Suggest Awesome GitHub Copilot Instructions Analyze current repository context and suggest relevant copilot-instruction files from the [GitHub awesome-copilot repository](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md) that are not already available in this repository. ## Process 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. ## 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: | 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 | | [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 | ## 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 ## 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: ```markdown --- description: 'Brief description of what this instruction provides' 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 - Read YAML front matter from local instruction files to extract descriptions and `applyTo` patterns - 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 - 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 - ❌ Not installed in repo

{ "prompt": "# Suggest Awesome GitHub Copilot Instructions\n\nAnalyze current repository context and suggest relevant copilot-instruction files from the [GitHub awesome-copilot repository](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md) that are not already available in this repository.\n\n## Process\n\n1. **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.\n2. **Scan Local Instructions**: Discover existing instruction files in `.github/instructions/` folder\n3. **Extract Descriptions**: Read front matter from local instruction files to get descriptions and `applyTo` patterns\n4. **Analyze Context**: Review chat history, repository files, and current project needs\n5. **Compare Existing**: Check against instructions already available in this repository\n6. **Match Relevance**: Compare available instructions against identified patterns and requirements\n7. **Present Options**: Display relevant instructions with descriptions, rationale, and availability status\n8. **Validate**: Ensure suggested instructions would add value not already covered by existing instructions\n9. **Output**: Provide structured table with suggestions, descriptions, and links to both awesome-copilot instructions and similar local instructions\n **AWAIT** user request to proceed with installation of specific instructions. DO NOT INSTALL UNLESS DIRECTED TO DO SO.\n10. **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.\n\n## Context Analysis Criteria\n\n🔍 **Repository Patterns**:\n- Programming languages used (.cs, .js, .py, .ts, etc.)\n- Framework indicators (ASP.NET, React, Azure, Next.js, etc.)\n- Project types (web apps, APIs, libraries, tools)\n- Development workflow requirements (testing, CI/CD, deployment)\n\n🗨️ **Chat History Context**:\n- Recent discussions and pain points\n- Technology-specific questions\n- Coding standards discussions\n- Development workflow requirements\n\n## Output Format\n\nDisplay analysis results in structured table comparing awesome-copilot instructions with existing repository instructions:\n\n| Awesome-Copilot Instruction | Description | Already Installed | Similar Local Instruction | Suggestion Rationale |\n|-----------------------------|-------------|-------------------|---------------------------|---------------------|\n| [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 |\n| [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 |\n| [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 |\n\n## Local Instructions Discovery Process\n\n1. List all `*.instructions.md` files in the `instructions/` directory\n2. For each discovered file, read front matter to extract `description` and `applyTo` patterns\n3. Build comprehensive inventory of existing instructions with their applicable file patterns\n4. Use this inventory to avoid suggesting duplicates\n\n## File Structure Requirements\n\nBased on GitHub documentation, copilot-instructions files should be:\n- **Repository-wide instructions**: `.github/copilot-instructions.md` (applies to entire repository)\n- **Path-specific instructions**: `.github/instructions/NAME.instructions.md` (applies to specific file patterns via `applyTo` frontmatter)\n- **Community instructions**: `instructions/NAME.instructions.md` (for sharing and distribution)\n\n## Front Matter Structure\n\nInstructions files in awesome-copilot use this front matter format:\n```markdown\n---\ndescription: 'Brief description of what this instruction provides'\napplyTo: '**/*.js,**/*.ts' # Optional: glob patterns for file matching\n---\n```\n\n## Requirements\n\n- Use `githubRepo` tool to get content from awesome-copilot repository\n- Scan local file system for existing instructions in `instructions/` directory\n- Read YAML front matter from local instruction files to extract descriptions and `applyTo` patterns\n- Compare against existing instructions in this repository to avoid duplicates\n- Focus on gaps in current instruction library coverage\n- Validate that suggested instructions align with repository's purpose and standards\n- Provide clear rationale for each suggestion\n- Include links to both awesome-copilot instructions and similar local instructions\n- Consider technology stack compatibility and project-specific needs\n- Don't provide any additional information or context beyond the table and the analysis\n\n## Icons Reference\n\n- ✅ Already installed in repo\n- ❌ Not installed in repo", "variables": [], "notes": "Suggest relevant GitHub Copilot instruction files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing instructions in this repository. Tools: edit, search, runCommands, runTasks, think, changes, testFailure, openSimpleBrowser, fetch, githubRepo, todos, search.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/lewismorgan/lewis", "path": ".github/prompts/suggest-awesome-github-copilot-instructions.prompt.md", "ref": "198cc529c3618208608804408dc2c9653889e1d1", "url": "https://github.com/lewismorgan/lewis/blob/198cc529c3618208608804408dc2c9653889e1d1/.github/prompts/suggest-awesome-github-copilot-instructions.prompt.md", "key": "lewismorgan/lewis/.github/prompts/suggest-awesome-github-copilot-instructions.prompt.md" } } }

suggest-awesome-github-copilot-instructions

About

Suggest Awesome GitHub Copilot Instructions

Process

Context Analysis Criteria

Output Format

Local Instructions Discovery Process

File Structure Requirements

Front Matter Structure

Requirements

Icons Reference

Use it

Manifest

Reviews