agent coding skill risk: low

Codebase Source Evidence Question Answering

Answer repository questions grounded entirely in source code evidence by searching files, reading content, and synthesizing responses with inline citations. Follow specified proced…

External action: low

SKILL 1 file

SKILL.md

Download

---
name: antigravity-awesome-skills-wiki-qa-98852f23
description: "Answer repository questions grounded entirely in source code evidence. Use when user asks a question about the codebase, user wants to understand a specific file, function, or component, or user asks /\"how does X work/\" or /\"where is Y defined/\"."
---
# 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.

## 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.

REQUIRED CONTEXT

user question about the codebase

ROLES & RULES

ONLY use information from actual source files
NEVER invent, guess, or use external knowledge
Think step by step before answering

EXPECTED OUTPUT

Format

markdown

Schema

markdown_sections · Key Files

Constraints

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
ONLY use information from actual source files
NEVER invent, guess, or use external knowledge

SUCCESS CRITERIA

Answer repository questions grounded entirely in source code evidence
Respond in the same language as the question
Synthesize an answer with inline citations
Include a Key Files table mapping files to their roles

FAILURE MODES

May invent or guess information not present in source files
May omit required Key Files table or inline citations

CAVEATS

Dependencies

codebase
source files

Missing context

Method or tools available for searching and reading files
Definition of what counts as valid "source code evidence"

Ambiguities

Duplicate "When to Use" section appears twice with slightly different wording.
"Search the codebase for relevant files" does not specify the mechanism or tools to use.

QUALITY

OVERALL: 0.81
CLARITY: 0.82
SPECIFICITY: 0.78
REUSABILITY: 0.88
COMPLETENESS: 0.80

IMPROVEMENT SUGGESTIONS

Remove the second redundant "When to Use" section to eliminate duplication.
Add an explicit step or note describing available tools or commands for searching/reading files.
Include a short example of a correctly formatted response with citations and Key Files table.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.