Practice the vocabulary of in-editor AI chat assistants and how they ground answers in real project context.
0 / 5 completed
1 / 5
At standup, a dev mentions asking an AI assistant embedded in the editor a question about a specific function without leaving the IDE. What is this feature called?
An in-editor AI chat assistant, like GitHub Copilot Chat, lets a developer ask questions about code directly within the IDE, with the assistant already aware of the open file and project context. This keeps the developer in their existing workflow instead of switching to a separate browser tab to look something up. It's a natural extension of inline code completion into a more conversational, question-driven interaction.
2 / 5
During a design review, the team wants the assistant's answer to be grounded in the specific files and symbols currently open, not just generic language knowledge. Which capability supports this?
Workspace-aware context grounding lets the assistant reference the specific files, symbols, and structure of the currently open project when answering a question, producing responses relevant to the actual codebase rather than only generic language-level advice. This context awareness is what distinguishes an in-editor assistant from a standalone chatbot with no visibility into the project. It generally requires the assistant to index or otherwise have access to the relevant files.
3 / 5
In a code review, a dev uses a chat command to ask the assistant to explain why a specific test is failing, referencing the actual error output. What does this represent?
Context-aware debugging assistance lets the assistant reference the actual error output and relevant code when explaining a test failure, producing a targeted diagnosis rather than a generic explanation of what that class of error usually means. This grounding in the specific failure significantly increases the practical usefulness of the response. It reflects the assistant's ability to combine general programming knowledge with the concrete details of the current problem.
4 / 5
An incident report shows a developer merged an AI-suggested code fix without reviewing it, and it introduced a subtle logic bug. What practice would prevent this?
Treating AI-suggested code as a draft that still requires the same review, testing, and scrutiny as any other proposed change catches subtle bugs before they reach production, regardless of how confident-sounding the suggestion was. Assuming the assistant's output is inherently correct skips the verification step that catches exactly this kind of subtle logic error. This review discipline applies to AI-generated code just as it does to code written by a human teammate.
5 / 5
During a PR review, a teammate asks why the team uses an in-editor AI chat assistant instead of searching documentation in a separate browser tab for every question. What is the reasoning?
Searching documentation in a separate browser tab interrupts the developer's flow and requires manually connecting generic documentation back to their specific code, while an in-editor assistant stays within the workflow and can reference the actual open project directly. This reduces context-switching overhead for routine questions encountered while coding. The tradeoff is that some questions, especially about broader ecosystem or non-code topics, may still be better served by external documentation.