What does Wiki Q&A do?

Wiki Q&A answers questions about your codebase by searching relevant files, reading them to gather facts, and synthesizing answers with inline citations showing exactly where each claim originates in the source code.

When should I use Wiki Q&A?

Use Wiki Q&A when you want to ask questions about your codebase, understand a specific file, function, or component, or ask how something works or where something is defined. Do not use it when you need environment-specific validation, testing, or expert review.

How does Wiki Q&A format its answers?

Wiki Q&A returns structured answers with inline citations in the format `(src/path/file.ts:42)` pointing to specific line numbers in your source code. If information is insufficient, it explicitly states this and suggests files to examine.

Does Wiki Q&A invent information or use external knowledge?

No—Wiki Q&A enforces a strict evidence-only approach and never invents, guesses, or uses external knowledge, making it reliable for users who require verifiable answers grounded entirely in actual source files.

Skill

Answer Codebase Questions with Source Evidence

Name: Wiki Q&A
Availability: OnlineOnly
Author: Antigravity

Answers codebase questions grounded entirely in source-code evidence, with inline file citations.

Get skill

Antigravity

Own this? Claim it

Spark score

out of 100

Updated today

Version 15.7.0

Add to Favorites

Why it matters

Understand your codebase by asking questions and receiving answers grounded solely in your source code. This skill helps developers quickly grasp the functionality and location of code elements.

Outcomes

What it gets done

Detect question language and respond in kind.

Search codebase for relevant files and extract evidence.

Synthesize answers with inline citations and key file mappings.

Identify insufficient information and suggest next steps.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-wiki-qa | bash

Overview

Wiki Q&A

Answers repository questions grounded entirely in source-code evidence, citing files inline and including a Key Files table, never inventing or guessing. Use it when a user asks a question about a codebase or wants to understand a specific file, function, or component.

What it does

Answers repository questions grounded entirely in source-code evidence: detects the question's language and responds in kind, searches the codebase for relevant files, reads them to gather evidence, and synthesizes an answer with inline citations. Responses use ## headings, language-tagged code blocks, tables, and bullet lists, cite sources inline as (src/path/file.ts:42), and include a "Key Files" table mapping files to their roles. If the available information is insufficient, it says so and suggests files to examine rather than guessing.

When to use - and when NOT to

Use it when a user asks a question about a codebase, wants to understand a specific file, function, or component, or asks "how does X work" or "where is Y defined."

Inputs and outputs

Input: a natural-language question about a repository. Output: a cited, evidence-grounded answer with a "Key Files" table, using only information found in the actual source files - never invented, guessed, or drawn from external knowledge.

Who it's for

Developers who want a codebase question answered with verifiable file-and-line citations rather than a plausible-sounding guess.

FAQ

Common questions

Discussion