Agent Skills
› microsoft/skills
› wiki-qa
wiki-qa
GitHub基于源码回答代码库相关问题，通过解析文件理解组件或导航代码。需先确定仓库上下文，严格依据源码证据生成带引用和图表的回答，禁止猜测。
Trigger Scenarios
用户询问代码库中某功能如何工作
用户希望了解特定文件或组件
用户询问某定义的位置
Install
npx skills add microsoft/skills --skill wiki-qa -g -y
SKILL.md
Frontmatter
{
"name": "wiki-qa",
"license": "MIT",
"metadata": {
"author": "Microsoft",
"version": "1.0.0"
},
"description": "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."
}
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](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](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
Version History
- 4f1db7e Current 2026-07-25 06:32
