documentation-style Skill
Formatting and style rules for markdown documentation. Use when generating or editing any project markdown document. Do not use for source code, code comments, or commit messages. For work item content (titles, descriptions, comments on GitHub Issues or Azure DevOps), use the Content Style section of the work-item-crea Published by microsoft in devsquad-copilot.
What is documentation-style Skill?
Formatting and style rules for markdown documentation. Use when generating or editing any project markdown document. Do not use for source code, code comments, or commit messages. For work item content (titles, descriptions, comments on GitHub Issues or Azure DevOps), use the Content Style section of the work-item-crea Published by microsoft in devsquad-copilot. 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
- Deployment
- Documentation
- Deployment use cases
- Documentation use cases
Technical details
- Install or run with Copy skill directory
When to use documentation-style Skill
- Use it for deployment.
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/devsquad-copilot
- Skill file: .github/plugins/devsquad/skills/documentation-style/SKILL.md
What it does
Formatting and style rules for markdown documentation. Use when generating or editing any project markdown document. Do not use for source code, code comments, or commit messages. For work item content (titles, descriptions, comments on GitHub Issues or Azure DevOps), use the Content Style section of the work-item-crea
Skill instructions
Documentation Style Guide This guide defines standards for all documentation generated in the project. Formatting - Ensure there are no spelling errors. Avoid emojis and decorative Unicode characters (such as →, •, ★, ✓, 🎯, ✅). - Avoid hyphens or dashes as separators between concepts. Instead of "concept A - concept B", rewrite the sentence. - Prefer lists and tables over long paragraphs. - Keep documents concise: specs and ADRs should be 1-2 pages, not novels. - Never use <number in free text (e.g., "1 priority", "3 option"). Azure DevOps automatically converts <number into a work item link. Use "first", "third option", or rephrase the sentence. Language - Avoid promotional or exaggerated language. - Do not use contrastive constructions: - "it's not just X, it's Y" - "it's not just about..." - "more than just..." - "goes beyond..." - Describe directly what something is, without negating or minimizing alternatives. - Use active voice and direct sentences. - Avoid generic framing: if t
Explore related resources
Frequently asked questions
What is documentation-style?
documentation-style is a open-source AI agent skill with Copy skill directory. Formatting and style rules for markdown documentation. Use when generating or editing any project markdown document. Do not use for source code, code comments, or commit messages.
Who is documentation-style best for?
documentation-style is best for reusing agent instructions, scripts, and references, deployment workflows, documentation workflows.
How do I install documentation-style?
Install or run documentation-style using Copy skill directory. Check documentation-style for the latest setup command.
Is documentation-style actively maintained?
documentation-style may need a closer maintenance check before production use.
Auto-fetched from GitHub.
