GitHub Copilot Vocabulary — Key Terms
Master the vocabulary developers use every day with GitHub Copilot: accepting and rejecting suggestions, using Copilot Chat, and talking about AI pair programming with your team.
0 / 25 completed
1 / 25
A teammate says: 'Copilot ___ a helper function I didn't write.' Which word belongs in the gap?
'Copilot suggested' is the standard phrase for describing code the AI proposed. It signals that the code came from AI, not the developer — important for team awareness and code review.
2 / 25
You press ___ to accept Copilot's ghost-text completion and insert it into the file.
Tab completion is the most common way to accept a Copilot suggestion. Pressing Tab inserts the full ghost-text suggestion at the cursor position.
3 / 25
A developer says: 'I ___ the suggestion because it used the wrong variable name.' What did they do?
Rejecting a suggestion means pressing Escape (or the reject key) to dismiss Copilot's ghost text. The developer can then write their own code or trigger a new suggestion.
4 / 25
Your colleague opens the Copilot ___ to ask the AI why a function returns null.
Copilot Chat is the dedicated conversational interface where developers can type questions, paste code, and receive detailed explanations or suggestions in a dialogue format.
5 / 25
You select a 30-line function and use Copilot to '___ ___ code'. What are you asking the AI to do?
'Explain this code' is a built-in Copilot Chat command that tells the AI to describe what a code selection does in plain English — useful for understanding unfamiliar code or onboarding new team members.
6 / 25
Reviewer: 'I'm seeing some pretty aggressive suggestions from Copilot in this PR. It keeps offering to refactor the entire `calculate_discount` function into a separate module—which isn't really needed and adds unnecessary complexity. I've marked it as 'insufficient' for now, but we should discuss how to manage these kinds of recommendations effectively. This scenario highlights the importance of critically evaluating Copilot's suggestions. Simply 'accepting' blindly can lead to unnecessary code changes and increased complexity. 'Rejecting' is too blunt; it doesn't address the underlying need for guidance. Flagging indicates a need for deeper understanding, while deferring suggests requesting clarification from the AI—a more strategic response in a code review context.
7 / 25
Reviewer: 'I'm noticing Copilot is frequently suggesting `extract_data` as the best approach for parsing JSON responses from our API. While it *does* work, the response format has changed recently and this method isn't handling the new fields correctly. I've marked this PR as insufficient, but let's talk about how we can configure Copilot to prioritize more robust parsing strategies. What is the reviewer primarily addressing regarding Copilot's suggestions?
This question focuses on a common issue with AI code completion – the risk of using outdated or inappropriate solutions. The reviewer isn't criticizing Copilot for generating *too much* code (option A), nor is it a general complaint about coding standards (option B). Instead, they're highlighting a specific problem: Copilot suggesting an incorrect method because the API documentation has changed, leading to potential errors. The core issue here is the importance of verifying and adapting AI suggestions based on real-time data and evolving requirements
(insufficient in this case signifies that the suggestion isn't currently valid).8 / 25
During a code review of a PR introducing a new API endpoint, Sarah comments: 'Copilot's offering to automatically generate the authentication headers feels…a little intrusive. I'm not entirely sure how it determined that specific authorization token.' Which phrasing best describes Sarah's concern?
Sarah is concerned that Copilot is acting without proper verification. 'Unverified' correctly captures her worry about the AI generating or suggesting authentication details without confirming they align with established security protocols and the correct authorization token. The other options misinterpret her concern - an 'opaque' suggestion implies secret generation, a 'transparent' one describes standard practice, and 'overzealous' is too strong of a descriptor for Copilot's action.
9 / 25
Reviewer: 'I'm seeing some potentially problematic suggestions from Copilot in this PR. It's repeatedly proposing to use the `fetch` API for all network requests—which is fine in principle, but we have a strict policy against using third-party libraries without thorough security audits. I've marked it as 'insufficient', and want to discuss our approach to evaluating these suggestions before moving forward.' Which term best describes the reviewer's concern regarding Copilot's recommendations?
The reviewer is primarily focused on 'compliance' – ensuring that their team adheres to pre-defined organizational policies and guidelines. The core issue isn't about performance (optimization), stylistic changes (refactoring), or the need to create documentation; it's about using approved tools and following security protocols, as dictated by the policy. This highlights a crucial aspect of Copilot usage: not blindly accepting suggestions but critically evaluating them against established standards.
10 / 25
John: "Hey, Copilot just suggested this entire function uses a `Promise` instead of a callback. It's cleaner, but I'm not sure if it's the right approach for our legacy system. Should we accept it?"This scenario highlights the importance of critically evaluating Copilot's suggestions, even when they appear beneficial. Simply accepting recommendations without understanding their implications can lead to integration problems or performance bottlenecks, particularly in older systems. Requesting more context ensures you understand the reasoning behind the suggestion and can assess its suitability for your specific project requirements.
John is asking a crucial question that demonstrates responsible usage.11 / 25
Reviewer: 'I'm seeing some pretty aggressive suggestions from Copilot in this PR. It keeps offering to refactor the entire `calculate_discount` function into a separate module—which isn't really needed and adds unnecessary complexity. I've marked it as 'insufficient' for now, but we should discuss how to manage these kinds of recommendations effectively. This scenario highlights the importance of critically evaluating Copilot's suggestions. Simply 'accepting' blindly can lead to unnecessary code changes and increased complexity. 'Rejecting' is too blunt; it doesn't address the underlying need for guidance. Flagging indicates a need for deeper understanding, while deferring suggests requesting clarification from the AI—a more strategic response in a code review context.
12 / 25
Reviewer: 'I'm noticing Copilot is frequently suggesting `extract_data` as the best approach for parsing JSON responses from our API. While it *does* work, the response format has changed recently and this method isn't handling the new fields correctly. I've marked this PR as insufficient, but let's talk about how we can configure Copilot to prioritize more robust parsing strategies. What is the reviewer primarily addressing regarding Copilot's suggestions?
This question focuses on a common issue with AI code completion – the risk of using outdated or inappropriate solutions. The reviewer isn't criticizing Copilot for generating *too much* code (option A), nor is it a general complaint about coding standards (option B). Instead, they're highlighting a specific problem: Copilot suggesting an incorrect method because the API documentation has changed, leading to potential errors. The core issue here is the importance of verifying and adapting AI suggestions based on real-time data and evolving requirements
(insufficient in this case signifies that the suggestion isn't currently valid).13 / 25
During a code review of a PR introducing a new API endpoint, Sarah comments: 'Copilot's offering to automatically generate the authentication headers feels…a little intrusive. I'm not entirely sure how it determined that specific authorization token.' Which phrasing best describes Sarah's concern?
Sarah is concerned that Copilot is acting without proper verification. 'Unverified' correctly captures her worry about the AI generating or suggesting authentication details without confirming they align with established security protocols and the correct authorization token. The other options misinterpret her concern - an 'opaque' suggestion implies secret generation, a 'transparent' one describes standard practice, and 'overzealous' is too strong of a descriptor for Copilot's action.
14 / 25
Reviewer: 'I'm seeing some potentially problematic suggestions from Copilot in this PR. It's repeatedly proposing to use the `fetch` API for all network requests—which is fine in principle, but we have a strict policy against using third-party libraries without thorough security audits. I've marked it as 'insufficient', and want to discuss our approach to evaluating these suggestions before moving forward.' Which term best describes the reviewer's concern regarding Copilot's recommendations?
The reviewer is primarily focused on 'compliance' – ensuring that their team adheres to pre-defined organizational policies and guidelines. The core issue isn't about performance (optimization), stylistic changes (refactoring), or the need to create documentation; it's about using approved tools and following security protocols, as dictated by the policy. This highlights a crucial aspect of Copilot usage: not blindly accepting suggestions but critically evaluating them against established standards.
15 / 25
John: "Hey, Copilot just suggested this entire function uses a `Promise` instead of a callback. It's cleaner, but I'm not sure if it's the right approach for our legacy system. Should we accept it?"This scenario highlights the importance of critically evaluating Copilot's suggestions, even when they appear beneficial. Simply accepting recommendations without understanding their implications can lead to integration problems or performance bottlenecks, particularly in older systems. Requesting more context ensures you understand the reasoning behind the suggestion and can assess its suitability for your specific project requirements.
John is asking a crucial question that demonstrates responsible usage.16 / 25
Reviewer: 'I'm seeing some pretty aggressive suggestions from Copilot in this PR. It keeps offering to refactor the entire `calculate_discount` function into a separate module—which isn't really needed and adds unnecessary complexity. I've marked it as 'insufficient' for now, but we should discuss how to manage these kinds of recommendations effectively. This scenario highlights the importance of critically evaluating Copilot's suggestions. Simply 'accepting' blindly can lead to unnecessary code changes and increased complexity. 'Rejecting' is too blunt; it doesn't address the underlying need for guidance. Flagging indicates a need for deeper understanding, while deferring suggests requesting clarification from the AI—a more strategic response in a code review context.
17 / 25
Reviewer: 'I'm noticing Copilot is frequently suggesting `extract_data` as the best approach for parsing JSON responses from our API. While it *does* work, the response format has changed recently and this method isn't handling the new fields correctly. I've marked this PR as insufficient, but let's talk about how we can configure Copilot to prioritize more robust parsing strategies. What is the reviewer primarily addressing regarding Copilot's suggestions?
This question focuses on a common issue with AI code completion – the risk of using outdated or inappropriate solutions. The reviewer isn't criticizing Copilot for generating *too much* code (option A), nor is it a general complaint about coding standards (option B). Instead, they're highlighting a specific problem: Copilot suggesting an incorrect method because the API documentation has changed, leading to potential errors. The core issue here is the importance of verifying and adapting AI suggestions based on real-time data and evolving requirements
(insufficient in this case signifies that the suggestion isn't currently valid).18 / 25
During a code review of a PR introducing a new API endpoint, Sarah comments: 'Copilot's offering to automatically generate the authentication headers feels…a little intrusive. I'm not entirely sure how it determined that specific authorization token.' Which phrasing best describes Sarah's concern?
Sarah is concerned that Copilot is acting without proper verification. 'Unverified' correctly captures her worry about the AI generating or suggesting authentication details without confirming they align with established security protocols and the correct authorization token. The other options misinterpret her concern - an 'opaque' suggestion implies secret generation, a 'transparent' one describes standard practice, and 'overzealous' is too strong of a descriptor for Copilot's action.
19 / 25
Reviewer: 'I'm seeing some potentially problematic suggestions from Copilot in this PR. It's repeatedly proposing to use the `fetch` API for all network requests—which is fine in principle, but we have a strict policy against using third-party libraries without thorough security audits. I've marked it as 'insufficient', and want to discuss our approach to evaluating these suggestions before moving forward.' Which term best describes the reviewer's concern regarding Copilot's recommendations?
The reviewer is primarily focused on 'compliance' – ensuring that their team adheres to pre-defined organizational policies and guidelines. The core issue isn't about performance (optimization), stylistic changes (refactoring), or the need to create documentation; it's about using approved tools and following security protocols, as dictated by the policy. This highlights a crucial aspect of Copilot usage: not blindly accepting suggestions but critically evaluating them against established standards.
20 / 25
John: "Hey, Copilot just suggested this entire function uses a `Promise` instead of a callback. It's cleaner, but I'm not sure if it's the right approach for our legacy system. Should we accept it?"This scenario highlights the importance of critically evaluating Copilot's suggestions, even when they appear beneficial. Simply accepting recommendations without understanding their implications can lead to integration problems or performance bottlenecks, particularly in older systems. Requesting more context ensures you understand the reasoning behind the suggestion and can assess its suitability for your specific project requirements.
John is asking a crucial question that demonstrates responsible usage.21 / 25
Reviewer: 'I'm seeing some pretty aggressive suggestions from Copilot in this PR. It keeps offering to refactor the entire `calculate_discount` function into a separate module—which isn't really needed and adds unnecessary complexity. I've marked it as 'insufficient' for now, but we should discuss how to manage these kinds of recommendations effectively. This scenario highlights the importance of critically evaluating Copilot's suggestions. Simply 'accepting' blindly can lead to unnecessary code changes and increased complexity. 'Rejecting' is too blunt; it doesn't address the underlying need for guidance. Flagging indicates a need for deeper understanding, while deferring suggests requesting clarification from the AI—a more strategic response in a code review context.
22 / 25
Reviewer: 'I'm noticing Copilot is frequently suggesting `extract_data` as the best approach for parsing JSON responses from our API. While it *does* work, the response format has changed recently and this method isn't handling the new fields correctly. I've marked this PR as insufficient, but let's talk about how we can configure Copilot to prioritize more robust parsing strategies. What is the reviewer primarily addressing regarding Copilot's suggestions?
This question focuses on a common issue with AI code completion – the risk of using outdated or inappropriate solutions. The reviewer isn't criticizing Copilot for generating *too much* code (option A), nor is it a general complaint about coding standards (option B). Instead, they're highlighting a specific problem: Copilot suggesting an incorrect method because the API documentation has changed, leading to potential errors. The core issue here is the importance of verifying and adapting AI suggestions based on real-time data and evolving requirements
(insufficient in this case signifies that the suggestion isn't currently valid).23 / 25
During a code review of a PR introducing a new API endpoint, Sarah comments: 'Copilot's offering to automatically generate the authentication headers feels…a little intrusive. I'm not entirely sure how it determined that specific authorization token.' Which phrasing best describes Sarah's concern?
Sarah is concerned that Copilot is acting without proper verification. 'Unverified' correctly captures her worry about the AI generating or suggesting authentication details without confirming they align with established security protocols and the correct authorization token. The other options misinterpret her concern - an 'opaque' suggestion implies secret generation, a 'transparent' one describes standard practice, and 'overzealous' is too strong of a descriptor for Copilot's action.
24 / 25
Reviewer: 'I'm seeing some potentially problematic suggestions from Copilot in this PR. It's repeatedly proposing to use the `fetch` API for all network requests—which is fine in principle, but we have a strict policy against using third-party libraries without thorough security audits. I've marked it as 'insufficient', and want to discuss our approach to evaluating these suggestions before moving forward.' Which term best describes the reviewer's concern regarding Copilot's recommendations?
The reviewer is primarily focused on 'compliance' – ensuring that their team adheres to pre-defined organizational policies and guidelines. The core issue isn't about performance (optimization), stylistic changes (refactoring), or the need to create documentation; it's about using approved tools and following security protocols, as dictated by the policy. This highlights a crucial aspect of Copilot usage: not blindly accepting suggestions but critically evaluating them against established standards.
25 / 25
John: "Hey, Copilot just suggested this entire function uses a `Promise` instead of a callback. It's cleaner, but I'm not sure if it's the right approach for our legacy system. Should we accept it?"This scenario highlights the importance of critically evaluating Copilot's suggestions, even when they appear beneficial. Simply accepting recommendations without understanding their implications can lead to integration problems or performance bottlenecks, particularly in older systems. Requesting more context ensures you understand the reasoning behind the suggestion and can assess its suitability for your specific project requirements.
John is asking a crucial question that demonstrates responsible usage.Frequently Asked Questions
What will I practice in "GitHub Copilot Vocabulary — Key Terms"?
This is an AI Code Generation Tools exercise set. It walks through 25 scenario-based multiple-choice questions built around real usage of AI Code Generation Tools terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 25 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the AI Code Generation Tools vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more AI Code Generation Tools exercises?
See the AI Code Generation Tools exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — AI Code Generation Tools vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.