Codebase Q&A Assistant

Ask how a repo works; get an explanation grounded in the code, with file and line pointers — not guesses.

Build an agent that answers questions about how a codebase works — "where is X handled?", "what does this module do?", "trace the request flow" — grounded in the repository itself. It uses GitHub to read the relevant files, then explains in plain technical language with pointers to the files and lines behind each statement, so a new contributor can follow the explanation straight into the code.

This is a single-tool read → grounded explanation pattern using markdown-header structure. Headers organize the answer (Summary, How it works, Where to look) for technical readers who scan. The defining design decision mirrors a good retrieval agent applied to code: explain only what the code shows, cite file and line, and when behavior depends on something not in view — config, a runtime dependency, an external service — name that gap rather than inventing the behavior. Edge cases cover very large repos (scope to paths), generated or vendored code, and questions the code can't answer.

This pattern applies anywhere people need to understand code they didn't write. Common scenarios for this pattern:

• Onboarding to an unfamiliar repository
• "Where is X handled?" navigation
• Dependency and call-flow tracing
• API-surface overviews
• Pre-contribution orientation

This manifest uses: GitHub

How to build single-shot agents using markdown headers prompt structure for narrative + file references output.

This agent manifest is sample code subject to Azure's licensing terms for Distributable Code under the Universal License Terms for Online Services .

IMPORTANT! This manifest is for educational and experimentation purposes. Resulting agents are not production ready. Review all provided resources and carefully test agent behavior in the context of your use case. Agents you create may be subject to legal and regulatory requirements, may require licenses, or may not be suitable for all industries, scenarios, or use cases. By using any manifest, you are acknowledging that resulting agents and other output are solely your responsibility, and that you will comply with all applicable laws, regulations, and relevant safety standards, terms of service, and codes of conduct. Learn more .