Back to Details

suggest-awesome-github-copilot-prompts

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Suggest Awesome GitHub Copilot Prompts

推荐优质GitHub Copilot提示

Analyze current repository context and suggest relevant prompt files from the GitHub awesome-copilot repository that are not already available in this repository.
分析当前仓库上下文，从GitHub awesome-copilot仓库中推荐本仓库尚未拥有的相关提示文件。

Process

流程

  1. Fetch Available Prompts: Extract prompt list and descriptions from awesome-copilot 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. 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
  1. 获取可用提示：从awesome-copilot README.prompts.md中提取提示列表和描述。必须使用
    #fetch
    工具。
  2. 扫描本地提示：发现
    .github/prompts/
    文件夹中已有的提示文件
  3. 提取描述：读取本地提示文件的前置元数据以获取描述信息
  4. 获取远程版本：对于每个本地提示，使用GitHub原始URL（例如：
    https://raw.githubusercontent.com/github/awesome-copilot/main/prompts/<filename>
    ）从awesome-copilot仓库获取对应的版本
  5. 版本对比：对比本地提示内容与远程版本，识别：
    • 已更新至最新版本的提示（完全匹配）
    • 过时的提示（内容存在差异）
    • 过时提示中的关键差异（工具、描述、内容）
  6. 上下文分析：查看聊天历史、仓库文件和当前项目需求
  7. 对比已有内容：检查本仓库中已有的提示
  8. 匹配相关性：将可用提示与识别出的模式和需求进行匹配
  9. 呈现选项：显示相关提示及其描述、推荐理由和可用性状态（包括过时提示）
  10. 验证：确保推荐的提示能够提供现有提示未覆盖的价值
  11. 输出：提供包含建议、描述以及指向awesome-copilot提示和类似本地提示链接的结构化表格 等待用户请求后再进行特定提示的安装或更新。除非收到明确指示，否则请勿进行安装或更新操作。
  12. 下载/更新资源：对于用户请求的提示，自动执行以下操作：
    • 将新提示下载至
      .github/prompts/
      文件夹
    • 用awesome-copilot中的最新版本替换过时的提示
    • 请勿调整文件内容
    • 使用
      #fetch
      工具下载资源，但也可使用
      #runInTerminal
      工具执行
      curl
      命令以确保获取所有内容
    • 使用
      #todos
      工具跟踪进度

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
🔍 仓库模式：
  • 使用的编程语言（.cs、.js、.py等）
  • 框架标识（ASP.NET、React、Azure等）
  • 项目类型（Web应用、API、库、工具）
  • 文档需求（README、规格说明、ADR）
🗨️ 聊天历史上下文：
  • 近期讨论和痛点
  • 功能请求或实现需求
  • 代码审查模式
  • 开发工作流要求

Output Format

输出格式

Display analysis results in structured table comparing awesome-copilot prompts with existing repository prompts:
Awesome-Copilot PromptDescriptionAlready InstalledSimilar Local PromptSuggestion Rationale
code-review.prompt.mdAutomated code review prompts❌ NoNoneWould enhance development workflow with standardized code review processes
documentation.prompt.mdGenerate project documentation✅ Yescreate_oo_component_documentation.prompt.mdAlready covered by existing documentation prompts
debugging.prompt.mdDebug assistance prompts⚠️ Outdateddebugging.prompt.mdTools configuration differs: remote uses 
'codebase'
vs local missing - Update recommended
以结构化表格形式展示分析结果，对比awesome-copilot提示与仓库中已有的提示：
Awesome-Copilot提示描述是否已安装类似本地提示推荐理由
code-review.prompt.md自动化代码审查提示❌ 未安装无可通过标准化代码审查流程优化开发工作流
documentation.prompt.md生成项目文档✅ 已安装create_oo_component_documentation.prompt.md现有文档提示已覆盖该功能
debugging.prompt.md调试辅助提示⚠️ 已过时debugging.prompt.md工具配置存在差异：远程版本使用
'codebase'
，而本地版本缺失 - 建议更新

Local Prompts Discovery Process

本地提示发现流程

  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
  1. 列出
    .github/prompts/
    目录下所有
    *.prompt.md
    文件
  2. 对于每个发现的文件，读取前置元数据以提取
    description
  3. 构建完整的现有提示清单
  4. 利用该清单避免推荐重复内容

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
  1. 对于每个本地提示文件，构建用于获取远程版本的GitHub原始URL：
    • 格式：
      https://raw.githubusercontent.com/github/awesome-copilot/main/prompts/<filename>
  2. 使用
    #fetch
    工具获取远程版本
  3. 对比整个文件内容（包括前置元数据和正文）
  4. 识别具体差异：
    • 前置元数据变更（描述、工具、模式）
    • 工具数组修改（添加、移除或重命名工具）
    • 内容更新（说明、示例、指南）
  5. 记录过时提示的关键差异
  6. 计算相似度以确定是否需要更新

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
  • 使用
    githubRepo
    工具从awesome-copilot仓库的提示文件夹获取内容
  • 扫描本地文件系统中
    .github/prompts/
    目录下的现有提示
  • 读取本地提示文件的YAML前置元数据以提取描述
  • 对比本地提示与远程版本以检测过时提示
  • 与本仓库中已有的提示进行对比以避免重复
  • 聚焦当前提示库的覆盖缺口
  • 验证推荐的提示是否符合仓库的用途和标准
  • 为每个建议提供清晰的理由
  • 包含指向awesome-copilot提示和类似本地提示的链接
  • 明确标记过时提示并注明具体差异
  • 除表格和分析内容外，请勿提供任何额外信息或上下文

Icons Reference

图标参考

  • ✅ 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
当识别出过时提示时：
  1. 在输出表格中用⚠️状态标记它们
  2. 在“推荐理由”列中记录具体差异
  3. 提供更新建议并注明关键变更
  4. 当用户请求更新时，用远程版本替换整个本地文件
  5. 保留文件在
    .github/prompts/
    目录中的位置