What problem does it solve? Developers often struggle to understand why code was written a certain way or how a system handles specific scenarios, especially in large or unfamiliar codebases. This Skill answers project-specific questions by retrieving relevant code chunks and curated knowledge entries, grounding every answer in traceable sources instead of guesswork. ## Core Features & Use Cases - Grounded Q&A: Queries the codekb_ask MCP tool to retrieve answers from code chunks, design decisions, and business rules with layered context assembly capped at 4K tokens. - Source Traceability: Every answer cites real file paths, line numbers, symbol names, and knowledge entry IDs so you can verify claims directly. - No-Fabrication Guard: Returns an explicit "not found in project" response when no relevant knowledge exists rather than inventing an answer. - Use Case: Ask "why does the messaging module use event-driven design" and receive an answer citing the relevant decision entry and the RefundController error-handling code. ## Quick Start Ask the assistant to use codekb-ask to explain how the system handles refund failures, including the cited source files.
