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
Click Get this skill. Grab the .md file, one click, no account needed.
Add it to Claude. Drop it into ~/.claude/skills/. Claude picks it up the next time you open a session.
Ask normally. Type your question. The skill triggers on the right keywords — you don't have to remember anything.
Generate unit tests for any function or class
Analyze test coverage gaps and suggest tests to write
Generate mocks, stubs, and fakes for dependencies
Create snapshot tests for UI components
Write end-to-end tests using Playwright or Cypress
Create test data factories and fixtures
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.