GitHub Copilot app for Beginners: Write your first prompt

GitHub · AI & ML ·

A beginner-oriented guide to using GitHub Copilot, written by one author across all segments. It covers prompt engineering fundamentals, onboarding steps for AI tools, and the iterative nature of human-AI interaction. Read 3 viewpoints with supporting evidence and source links.

Understand this piece

3 key points

Synthesis

  1. Start with a plain description—not perfect syntax

    A prompt is simply a description of what you want to accomplish. You don’t need special syntax or perfect phrasing—start with what you know and refine as you go.

    Supporting evidence 1

    Original excerpt

    A prompt is simply a description of what you want to accomplish. Start with what you know, give Copilot some context, and refine the request as you go.

    Kayla Cinnamon · Paragraph 2

    Context

    The good news is that you don’t need to write the perfect prompt to get started.

    Read in source context →
  2. Provide codebase context before prompting

    Before asking Copilot to make a change, connect it to a GitHub repository or local folder so it can access the relevant code and files.

    Supporting evidence 1

    Original excerpt

    Before you can ask Copilot to make a change, it needs something to work on. Agent sessions can be connected to a GitHub repository or a folder on your local machine, giving Copilot access to the code and files it needs for the task.

    Kayla Cinnamon · Paragraph 5

    Read in source context →

    Continue exploring

    AI tool onboarding →
  3. Prompting is iterative—not all details needed upfront

    If the first output isn’t quite right, add details or request changes; prompting doesn’t require anticipating every detail before beginning.

    Supporting evidence 1

    Original excerpt

    If the first attempt isn’t quite what you had in mind, you can provide additional details or ask for changes. Prompting is an iterative process, so you don’t have to anticipate every detail before you begin.

    Kayla Cinnamon · Paragraph 13

    Read in source context →

Key passages3

Attributed passages with the context to verify them. Open the original text to check the source.

prompt engineering for beginners

Start with a plain description—not perfect syntax

Original excerpt

A prompt is simply a description of what you want to accomplish. Start with what you know, give Copilot some context, and refine the request as you go.
Context

The good news is that you don’t need to write the perfect prompt to get started.

iterative AI interaction

Prompting is iterative—not all details needed upfront

Original excerpt

If the first attempt isn’t quite what you had in mind, you can provide additional details or ask for changes. Prompting is an iterative process, so you don’t have to anticipate every detail before you begin.
AI tool onboarding

Provide codebase context before prompting

Original excerpt

Before you can ask Copilot to make a change, it needs something to work on. Agent sessions can be connected to a GitHub repository or a folder on your local machine, giving Copilot access to the code and files it needs for the task.

Mentioned here

All mentioned things

GitHub Copilot

Mention only

The text provides instructional guidance on how to write prompts for GitHub Copilot, describing it as a tool that accepts natural language descriptions.

Read supporting evidence · Kayla Cinnamon
Mention only

The excerpt explains the technical requirement of connecting GitHub Copilot to repositories or local folders to enable agent sessions.

Read supporting evidence · Kayla Cinnamon

Source & methodology

These viewpoints are linked to their original sources. Paraphrases are labeled and are not verbatim quotes.

Open transcript or source material (opens in a new tab)Report an issue

Explore these viewpoints by person