wiki-onboarding
Wiki Onboarding Guide Generator
Generate four audience-tailored onboarding documents in an onboarding/ folder, each giving a different stakeholder exactly the understanding they need.
Source Repository Resolution (MUST DO FIRST)
Before generating any guides, you MUST determine the source repository context:
- Check for git remote: Run
git remote get-url originto detect if a remote exists - Ask the user: "Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?"
- Remote URL provided → store as
REPO_URL, use linked citations:[file:line](REPO_URL/blob/BRANCH/file#Lline) - Local-only → use local citations:
(file_path:line_number)
- Remote URL provided → store as
- Determine default branch: Run
git rev-parse --abbrev-ref HEAD - Do NOT proceed until source repo context is resolved
When to Activate
- User asks for onboarding docs or getting-started guides
- User runs
/deep-wiki:onboardcommand
More from microsoft/skills
frontend-design-review
>
47skill-creator
Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating existing skills.
43cloud-solution-architect
>-
33mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP), Node/TypeScript (MCP SDK), or C#/.NET (Microsoft MCP SDK).
31continual-learning
Guide for implementing continual learning in AI coding agents — hooks, memory scoping, reflection patterns. Use when setting up learning infrastructure for agents.
26microsoft-docs
Understand Microsoft technologies by querying official documentation. Use whenever the user asks how something works, wants tutorials, needs configuration options, limits, quotas, or best practices for any Microsoft technology (Azure, .NET, M365, Windows, Power Platform, etc.)—even if they don't mention "docs." If the question is about understanding a concept rather than writing code, this is the right skill.
23