Skip to main content

copilot-vscode-docs

Comprehensive research and grounding of answers using official VS Code and GitHub Copilot documentation. Use before conducting web searches for VS Code features, Copilot capabilities, configuration, debugging, extensions, remote development, or any official Microsoft documentation queries.

跳到安装

来源信息

仓库
arisng/github-copilot-fc
最近来源活动
2026年3月12日 15:50
检测到的 SKILL.md 语言
英语
星标
5
分支
0

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

文件资源管理器
7 个文件

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
copilot-vscode-docs
description
Comprehensive research and grounding of answers using official VS Code and GitHub Copilot documentation. Use before conducting web searches for VS Code features, Copilot capabilities, configuration, debugging, extensions, remote development, or any official Microsoft documentation queries.
metadata
{"version":"1.0.0","author":"arisng"}
# VS Code Documentation Research Skill Research and ground answers using official VS Code and GitHub Copilot documentation. Provides access to current release notes, feature documentation, and specialized content. ## Core Workflow 1. **Analyze Query**: Identify VS Code/Copilot features, configuration, or troubleshooting needs 2. **Navigate Structure**: Use `assets/toc.md` to locate relevant documentation sections 3. **Retrieve Content**: Fetch specific pages using web tools when detailed information required 4. **Ground Response**: Base answers on official documentation with citations and links ## Key Resources - **Documentation TOC**: `assets/toc.md` - Complete structure for navigation - **Official URLs**: See [RESOURCES.md](references/resources.md) for canonical links - **Expertise Areas**: See [KEY-AREAS.md](references/key-areas.md) for detailed coverage - **Prompt Files**: See [prompt-files.md](references/prompt-files.md) for current Prompt File Engineering standards - **Usage Examples**: See [WORKFLOW-EXAMPLES.md](references/workflow-examples.md) for concrete scenarios ## Tool Integration - Use web fetching tools for specific documentation pages - Execute `scripts/parse_toc.py` to refresh documentation structure - Read reference files as needed for comprehensive coverage ## Best Practices - Always prefer official documentation over assumptions - Cite specific URLs and version numbers - Check release notes for recent feature changes - Use TOC navigation for comprehensive topic coverage - Validate answers against current documentation before responding
在 GitHub 查看