Skip to main content

GitHub Copilot– Reusable prompts files

Yesterday I talked about custom instructions as a general way to influence the behavior of Github Copilot in multiple contexts(coding, testing, reviewing, ...) in VS Code. With prompt files you can go one step further, and provide specific instructions for a task.

Let’s give this feature a try.

Active the prompts file feature

First we need to activate this feature:

  • Go to File –> Preferences –> Settings.
  • Search for Chat and look for the Prompt files setting.
  • Click on the Edit in settings.json link.

  • The settings.json file is opened with a new chat.promptFiles setting already added.
  • Change the value to true. Now VSCode will look for prompt files in the .github/prompts folder.

 

    Creating a prompt file

    Now we are ready to add one or more prompts file to the .github/prompts folder.

    For every task you should create a separate Markdown prompt file.

    Remark: It is possible to reference other files inside your Markdown prompt file as well:

    Using a prompt file

    Now we can use our newly created prompt files.

    • Open the VSCode Copilot Chat window:

     

    • Select the Attach Context icon (Ctrl+/), and then select Prompt....

     

    • Choose a prompt file from the Quick Pick to attach it to your chat request.

     

    • Now we can either directly send the prompt or include other instructions.

     

    More information

    Custom instructions for GitHub Copilot in VS Code

    Popular posts from this blog

    Podman– Command execution failed with exit code 125

    After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

    Azure DevOps/ GitHub emoji

    I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

    VS Code Planning mode

    After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...