# Copilot Vscode Docs

> ---

- Skill: `arisng/copilot-vscode-docs` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx skillmds@latest add arisng/copilot-vscode-docs`
- Raw SKILL.md: https://api.skillmd.com/api/skills/arisng/copilot-vscode-docs/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: arisng (https://skillmd.com/u/arisng)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/arisng/copilot-vscode-docs

---

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