doc-writer Skill
Plan and write VS Code documentation for a new or updated feature. ALWAYS use this skill when the user asks to "document", "add docs for", "write docs for", or "update the docs for" a feature, or provides a GitHub issue/PR link to document — even if the change seems small. Proposes a documentation plan and asks clarify Published by microsoft in vscode-docs.
What is doc-writer Skill?
Plan and write VS Code documentation for a new or updated feature. ALWAYS use this skill when the user asks to "document", "add docs for", "write docs for", or "update the docs for" a feature, or provides a GitHub issue/PR link to document — even if the change seems small. Proposes a documentation plan and asks clarify Published by microsoft in vscode-docs. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Writing
- Documentation use cases
- Writing use cases
Technical details
- Install or run with Copy skill directory
When to use doc-writer Skill
- Use it for documentation.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-docs
- Skill file: .github/skills/doc-writer/SKILL.md
What it does
Plan and write VS Code documentation for a new or updated feature. ALWAYS use this skill when the user asks to "document", "add docs for", "write docs for", or "update the docs for" a feature, or provides a GitHub issue/PR link to document — even if the change seems small. Proposes a documentation plan and asks clarify
Skill instructions
Document a Feature Help document a new or updated VS Code feature in the project documentation (the docs/ folder). This skill works in two phases: it first researches the feature and proposes a documentation plan, then implements the changes only after you approve. It is acceptable to conclude that no documentation update is needed. When to Use Use this skill whenever the request maps to any of these — do not start editing docs directly without first running Phase 1: The user says "document this", "document this functionality/feature", "add docs for…", "write docs for…", or "update the docs for…". The user pastes a GitHub issue or PR link and asks you to document or address it in the docs. Documenting a new or changed VS Code or GitHub Copilot feature. Turning a GitHub issue or PR into concrete docs/ updates. Auditing whether existing docs need updating after a feature change. This applies even when the change looks small (a clarification, a few added steps, a single section). Run the
Explore related resources
Frequently asked questions
What is doc-writer?
doc-writer is a open-source AI agent skill with Copy skill directory. Plan and write VS Code documentation for a new or updated feature. ALWAYS use this skill when the user asks to "document", "add docs for", "write docs for", or "update the docs for" a feature, or provides a.
Who is doc-writer best for?
doc-writer is best for reusing agent instructions, scripts, and references, documentation workflows, writing workflows.
How do I install doc-writer?
Install or run doc-writer using Copy skill directory. Check doc-writer for the latest setup command.
Is doc-writer actively maintained?
doc-writer may need a closer maintenance check before production use.
Auto-fetched from GitHub.
