What problem does it solve? New engineers lose weeks hunting through unfamiliar codebases for answers, and vague guidance without file references leaves them unable to self-serve the next question. This Skill grounds every answer in the repository's own docs and code, always citing the exact file path and line. ## Core Features & Use Cases - Path-cited answers: Every response points to a concrete location like backend/app/services/skills.py:391 instead of a paraphrase, teaching engineers where things live. - Question-behind-the-question reasoning: Recognizes that "How do I add an endpoint?" usually means "what will review reject?" and answers both. - Enforced vs. convention distinction: Separates what tests and linters block from what reviewers merely mention, so engineers know what actually gates a merge. - Stale doc detection: Flags when documentation contradicts the code and states what the code actually does. - Use Case: A new hire asks how to add an API endpoint and receives the route location, the two conventions reviewers flag, and which checks are enforced by CI versus informal. ## Quick Start Ask the agent how to add a new endpoint in this repository and request the exact file paths and review conventions involved.
