
wiki-qa
โ Officialโ 2,676by microsoft ยท part of microsoft/skills
Answers questions about a code repository using source file analysis. Use when the user asks a question about how something works, wants to understand a component, or needs help navigating the codebase.
This is the playbook your agent receives when the skill activates โ you don't need to read it to use the skill, but it's here to audit before installing.
Wiki Q&A
Answer repository questions grounded entirely in source code evidence.
When to Activate
- User asks a question about the codebase
- User wants to understand a specific file, function, or component
- User asks "how does X work" or "where is Y defined"
Source Repository Resolution (MUST DO FIRST)
Before answering any question, 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](https://github.com/microsoft/skills/blob/main/.github/plugins/deep-wiki/skills/wiki-qa/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
Procedure
- Resolve source repo context (see above)
- Detect the language of the question; respond in the same language
- Search the codebase for relevant files
- Read those files to gather evidence
- Synthesize an answer with inline linked citations
Response Format
- Use
##headings, code blocks with language tags, tables, bullet lists - Cite sources inline using resolved format:
- Remote:
[src/path/file.ts:42](https://github.com/microsoft/skills/blob/main/.github/plugins/deep-wiki/skills/wiki-qa/REPO_URL/blob/BRANCH/src/path/file.ts#L42) - Local:
(src/path/file.ts:42)
- Remote:
- Include a "Key Files" table mapping files to their roles (with linked citations in the "File" column)
- Include at least 1 Mermaid diagram when the answer involves architecture, data flow, or relationships โ a diagram makes the answer 10x more useful
- Use tables for any structured data in the answer (component lists, API endpoints, config options, comparisons)
- If information is insufficient, say so and suggest files to examine
Rules
- ONLY use information from actual source files
- NEVER invent, guess, or use external knowledge
- Think step by step before answering
npx skills add microsoft/skills --skill "wiki-qa" --full-depthRun this in your project โ your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.
Licensed under MITโ you can use, modify, and redistribute it under that license's terms.
View the full license file on GitHub โ