Skip to main content
AI/MLsickn33

wiki-qa

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\".

Stars
39,227
Source
sickn33/antigravity-awesome-skills
Updated
2026-05-30
Slug
sickn33--antigravity-awesome-skills--wiki-qa
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/sickn33/antigravity-awesome-skills/HEAD/plugins/antigravity-awesome-skills-claude/skills/wiki-qa/SKILL.md -o .claude/skills/wiki-qa.md

Drops the SKILL.md into .claude/skills/wiki-qa.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

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.