Provides grounded answers to questions about the repository based on direct source code evidence.

Install

mkdir -p .claude/skills/wiki-qa-anhvu1107 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14866" && unzip -o skill.zip -d .claude/skills/wiki-qa-anhvu1107 && rm skill.zip

Installs to .claude/skills/wiki-qa-anhvu1107

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

ALWAYS use this when the request matches Wiki QA: Answer repository questions grounded entirely in source code evidence.
120 chars✓ has a “when” trigger
Beginner

Key capabilities

  • Search the codebase for relevant files
  • Read files to gather evidence
  • Synthesize answers with inline citations
  • Detect the language of the question and respond in kind
  • Provide answers grounded entirely in source code

How it works

The skill searches codebase files, reads them for evidence, and synthesizes an answer with inline citations.

Inputs & outputs

You give it
Question about the codebase
You get back
Answer with inline citations to source code

When to use wiki-qa

  • Explain how a feature works
  • Find where a function is defined
  • Understand code logic
  • Retrieve file-specific documentation

About this skill

Wiki Q&A

Selective Reading Rule

Start with:

  • references/senior-master-standard.md
  • references/usage-routing.md
  • references/quality-checklist.md

Then load only the inherited docs, scripts, assets, or examples that match the user's actual task.

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.

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.

When not to use it

  • The user needs information not present in the source files.
  • The task requires inventing or guessing information.
  • The task involves using external knowledge.

Limitations

  • This skill ONLY uses information from actual source files.
  • This skill NEVER invents, guesses, or uses external knowledge.
  • If information is insufficient, the skill states so.

How it compares

This skill provides answers strictly from source code evidence, unlike general knowledge retrieval.

Compared to similar skills

wiki-qa side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
wiki-qa (this skill)03moNo flagsBeginner
react-expert86moReviewAdvanced
rust-learner86moReviewBeginner
cartographer36moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

react-expert

reactjs

Use when researching React APIs or concepts for documentation. Use when you need authoritative usage examples, caveats, warnings, or errors for a React feature.

823

rust-learner

actionbook

Use when asking about Rust versions or crate info. Keywords: latest version, what's new, changelog, Rust 1.x, Rust release, stable, nightly, crate info, crates.io, lib.rs, docs.rs, API documentation, crate features, dependencies, which crate, what version, Rust edition, edition 2021, edition 2024, cargo add, cargo update, 最新版本, 版本号, 稳定版, 最新, 哪个版本, crate 信息, 文档, 依赖, Rust 版本, 新特性, 有什么特性

83

cartographer

kingbootoshi

Maps and documents codebases of any size by orchestrating parallel subagents. Creates docs/CODEBASE_MAP.md with architecture, file purposes, dependencies, and navigation guides. Updates CLAUDE.md with a summary. Use when user says "map this codebase", "cartographer", "/cartographer", "create codebase map", "document the architecture", "understand this codebase", or when onboarding to a new project. Automatically detects if map exists and updates only changed sections.

37

repo-research-analyst

parcadei

Analyze repository structure, patterns, conventions, and documentation for understanding a new codebase

16

exploring-rust-crates

hashintel

Generate Rust documentation to understand crate APIs, structure, and usage. Use when exploring Rust code, understanding crate organization, finding functions/types/traits, or needing context about a Rust package in the HASH workspace.

33

investigation

talmolab

Scaffolds a structured investigation in scratch/ for empirical research and documentation. Use when the user says "start an investigation" or wants to: trace code paths or data flow ("trace from X to Y", "what touches X", "follow the wiring"), document system architecture comprehensively ("document how the system works", "archeology"), investigate bugs ("figure out why X happens"), explore technical feasibility ("can we do X?"), or explore design options ("explore the API", "gather context", "design alternatives"). Creates dated folder with README. NOT for simple code questions or single-file searches.

30

Search skills

Search the agent skills registry