suggest-awesome-github-copilot-prompts

github/awesome-copilot

Suggest relevant GitHub Copilot prompts from awesome-copilot based on your repository context and identify outdated prompts.

Source View on skills.sh

What is suggest-awesome-github-copilot-prompts?

This skill analyzes your repository's context, chat history, and existing prompts to recommend relevant prompt files from the GitHub awesome-copilot repository. It identifies gaps in your prompt library, detects outdated prompts that need updates, and avoids suggesting duplicates.

Fetches available prompts from the awesome-copilot repository and compares them against your local `.github/prompts/` directory
Detects outdated prompts by comparing local versions with remote versions and identifies specific differences in tools, descriptions, and content
Analyzes repository patterns (languages, frameworks, project type) and chat history to determine which prompts would be most relevant
Presents suggestions in a structured table showing installation status, similar local prompts, and rationale for each recommendation
Automatically downloads new prompts or updates outdated ones when you request installation

How to install suggest-awesome-github-copilot-prompts

npx skills add https://github.com/github/awesome-copilot --skill suggest-awesome-github-copilot-prompts

Prerequisites

Access to a GitHub repository with a `.github/prompts/` directory (will be created if it doesn't exist)
GitHub Copilot or compatible AI coding agent installed

Claude Code

Cursor

Windsurf

Cline

How to use suggest-awesome-github-copilot-prompts

1.Run the skill to analyze your repository context and existing prompts
2.Review the generated table showing awesome-copilot prompts with their installation status and relevance to your project
3.Identify any outdated prompts marked with ⚠️ and note the specific differences highlighted
4.Request installation or updates for prompts you want to add or update
5.The skill will download new prompts to `.github/prompts/` or replace outdated versions with the latest from awesome-copilot

Use cases

Good for

Discover code review, documentation, or debugging prompts that match your project's tech stack and development workflow
Identify when your existing prompts are outdated and need updates from the latest awesome-copilot versions
Find specialized prompts for your specific language or framework (e.g., C#, Python, React) that aren't yet in your repository
Avoid duplicate prompt installations by checking what's already available locally before suggesting new ones
Maintain a curated, up-to-date prompt library tailored to your team's needs

Who it's for

Development teams using GitHub Copilot who want to build a curated prompt library
Projects seeking to standardize code review, documentation, and debugging workflows
Teams managing multiple repositories and wanting consistent prompt usage across projects

suggest-awesome-github-copilot-prompts FAQ

What happens if I already have a prompt with the same name as one in awesome-copilot?

The skill detects this and marks it as already installed. It will compare versions to check if your local copy is up-to-date or outdated, and only suggest an update if the remote version differs.

Will this skill automatically install prompts without asking?

No. The skill analyzes and suggests prompts, then waits for your explicit request before downloading or updating any files.

How does the skill determine which prompts are relevant to my project?

It analyzes your repository's programming languages, frameworks, project type, and your recent chat history to match against available prompts and identify gaps in coverage.

What if a prompt is outdated—how do I know what changed?

The skill documents specific differences (tools, descriptions, content changes) in the suggestion rationale column so you can decide whether to update.

Can I use this with repositories that don't have a `.github/prompts/` directory yet?

Yes. The skill will work with your repository structure and can create the directory if needed when you request prompt installation.

Full instructions (SKILL.md)

Source of truth, from github/awesome-copilot.

name: suggest-awesome-github-copilot-prompts 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.'

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 #fetch tool.
Scan Local Prompts: Discover existing prompt files in .github/prompts/ folder
Extract Descriptions: Read front matter from local prompt files to get descriptions
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>)
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)
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 including outdated prompts
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 or updates of specific prompts. DO NOT INSTALL OR UPDATE UNLESS DIRECTED TO DO SO.
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

🔍 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.prompt.md	Automated code review prompts	❌ No	None	Would enhance development workflow with standardized code review processes
documentation.prompt.md	Generate project documentation	✅ Yes	create_oo_component_documentation.prompt.md	Already covered by existing documentation 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

List all *.prompt.md files in .github/prompts/ directory
For each discovered file, read front matter to extract description
Build comprehensive inventory of existing prompts
Use this inventory to avoid suggesting duplicates

Version Comparison Process

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>
Fetch the remote version using the #fetch tool
Compare entire file content (including front matter and body)
Identify specific differences:
- Front matter changes (description, tools, mode)
- Tools array modifications (added, removed, or renamed tools)
- Content updates (instructions, examples, guidelines)
Document key differences for outdated prompts
Calculate similarity to determine if update is needed

Requirements

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