mcpField
W
wiki-qa

wiki-qa

github.com/sickn33Development48.7k91 installsUpdated today
Repository

About wiki-qa

A skill for answering repository questions using source-code evidence only, with inline file and line citations. It is intended for developers investigating files, functions, or components.

Key features

  1. 01Search and read relevant source files
  2. 02Synthesize answers from code evidence
  3. 03Cite files and line numbers inline
  4. 04Identify files to inspect when evidence is insufficient

Use cases

  1. 01Trace how a function or component works
  2. 02Locate a definition in a repository
  3. 03Answer codebase questions from source

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill wiki-qa

After installing, type/wiki-qain Claude Code to confirm it loaded.

Details

From the project README

Wiki Q&A

Answer repository questions grounded entirely in source code evidence.

When to Use

  • 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"

Procedure

  1. Detect the language of the question; respond in the same language
  2. Search the codebase for relevant files
  3. Read those files to gather evidence
  4. Synthesize an answer with inline citations

Response Format

  • Use ## headings, code blocks with language tags, tables, bullet lists
  • Cite sources inline: (src/path/file.ts:42)
  • Include a "Key Files" table mapping files to their roles
  • 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
When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Example

User request:

Answer this repository question using only source-code evidence, with direct file and line references.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported