microsoft/docs-product-alignment
.github/skills/docs-product-alignment/SKILL.md
Audit and update docs/copilot/ documentation to accurately reflect current VS Code AI capabilities. Use when: competitive analysis reveals gaps, product launches new features, docs use outdated framing, or keyword coverage needs strengthening for discoverability by users and AI agents. Produces a gap analysis plus targeted edits across affected files.
$ install --global
skillsauthnpx skillsauth add microsoft/vscode-docs docs-product-alignmentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 7, 2026, 8:25 AM103.4s1 file scanned
SKILL.md
- name:
- docs-product-alignment
- description:
- Audit and update docs/copilot/ documentation to accurately reflect current VS Code AI capabilities. Use when: competitive analysis reveals gaps, product launches new features, docs use outdated framing, or keyword coverage needs strengthening for discoverability by users and AI agents. Produces a gap analysis plus targeted edits across affected files.
Documentation Product Alignment
Audit VS Code Copilot documentation against current product capabilities and produce targeted, style-compliant edits. Follow the docs-writing style guide for all writing rules.
Guardrails
- Factual only. Every claim must map to something the product does today. No superlatives, no competitive comparisons, no invented terminology.
- Two audiences. Humans read the prose; AI agents and search crawlers index Keywords, MetaDescriptions, and opening paragraphs. Both matter.
- Minimal edits. Change only what is inaccurate, outdated, or missing. One precise sentence beats a rewritten section.
- Verifiable. If you cannot point to a UI element, setting, or documented behavior, do not write it.
Workflow
- Gather context. Read the latest release notes, check github.com/features/copilot, and review any competitive claims or feature matrices the user provides.
- Audit high-traffic pages. Read each page and compare against current product truth. Focus on MetaDescriptions, Keywords, opening paragraphs, and terminology.
- Gap analysis. List what is inaccurate, outdated, or missing. Map each gap to a file and location. Prioritize by page traffic.
- Edit. Apply targeted changes. Vary phrasing across pages to avoid repetition.
- Verify. Search changed files for banned words, em-dashes, and MetaDescription length violations.
High-traffic pages to always check:
- docs/copilot/overview.md, docs/copilot/concepts/overview.md, docs/copilot/reference/copilot-vscode-features.md
- docs/copilot/getting-started.md, docs/copilot/agents/overview.md
- docs/copilot/reference/workspace-context.md, docs/copilot/faq.md
Terminology
Use these terms consistently. The "Avoid" column lists terms that creep in but should not.
| Concept | Use | Avoid | |---------|-----|-------| | Autonomous coding sessions | agents | agent mode, agentic workflows | | Running without user interaction | background agents | background agent mode | | Code suggestions as you type | inline suggestions | code completions, autocomplete | | Predicted next edit location | next edit suggestions (NES) | predictive edits | | Understanding code across files | workspace context, cross-file reasoning | deep semantic understanding (overuse) | | GitHub's search for code context | GitHub's code search | remote search | | VS Code's type/symbol analysis | language intelligence (IntelliSense, LSP) | code intelligence | | Multiple AI model options | multiple AI models | leading AI models | | Plan then implement workflow | Plan agent, implementation agent | planning mode |
Capability areas
When auditing, ensure docs accurately cover these areas:
- Agents: plan, implement, verify, parallel sessions, local/background/cloud, third-party support
- Context: semantic search, language intelligence (LSP), GitHub code search, cross-repo awareness
- Multi-file editing: coordinated changes, architecture-level refactoring, framework migrations
- Enterprise: organization policies, model access controls, content exclusions, trust boundaries
- SDLC workflow: Plan agent, implementation agent, Copilot code review, background/cloud handoff
- Scale: large codebases, monorepos, multi-root workspaces, remote indexing
Related Skills
microsoft/release-note-writer
development
VerifiedTrustedCommunity
Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.
6,448SKILL.mdUpdated Apr 7, 2026
microsoft/release-note-reviewer
development
VerifiedTrustedCommunity
Review VS Code release notes for style, structure, and completeness. Use for reviewing Insiders or Stable release notes against writing guidelines. Produces an actionable list of recommendations.
6,448SKILL.mdUpdated Apr 7, 2026
microsoft/frontmatter-description
development
VerifiedTrustedCommunity
Check and optimize MetaDescription frontmatter fields in VS Code documentation. Use when auditing, adding, or improving page descriptions for SEO and discoverability. Apply this when making content changes to markdown articles.
6,448SKILL.mdUpdated Apr 7, 2026
microsoft/content-redirect
development
VerifiedTrustedCommunity
Create and manage redirects in VS Code documentation when pages are moved, renamed, or deleted. Use when moving docs pages, renaming files, restructuring content, or when the user asks about redirects.
6,448SKILL.mdUpdated Apr 7, 2026