aa71e76eb9
- Add date_added to all 950+ skills for complete tracking - Update version to 6.5.0 in package.json and README - Regenerate all indexes and catalog - Sync all generated files Features from merged PR #150: - Stars/Upvotes system for community-driven discovery - Auto-update mechanism via START_APP.bat - Interactive Prompt Builder - Date tracking badges - Smart auto-categorization All skills validated and indexed. Made-with: Cursor
41 lines
1.3 KiB
Markdown
41 lines
1.3 KiB
Markdown
---
|
|
name: wiki-qa
|
|
description: "Answers questions about a code repository using source file analysis. Use when the user asks a question about how something works, wants to understand a component, or needs help navigating the code..."
|
|
risk: unknown
|
|
source: community
|
|
date_added: "2026-02-27"
|
|
---
|
|
|
|
# Wiki Q&A
|
|
|
|
Answer repository questions grounded entirely in source code evidence.
|
|
|
|
## When to Activate
|
|
|
|
- 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.
|