AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

wiki-qa

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.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read microsoft--wiki-qa at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 1

SKILL.md

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:

  1. Check for git remote: Run git remote get-url origin to detect if a remote exists
  2. 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)
  3. Determine default branch: Run git rev-parse --abbrev-ref HEAD
  4. Do NOT proceed until source repo context is resolved

Procedure

  1. Resolve source repo context (see above)
  2. Detect the language of the question; respond in the same language
  3. Search the codebase for relevant files
  4. Read those files to gather evidence
  5. 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)
  • 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