Skip to main content

Context is key–Add instructions to your copilot-instructions.md file

The best way to improve the results you get back from GitHub Copilot, is by providing it some extra context. I explained before how you could use the copilot-instructions.md for this or by creating re-usable custom prompts.

When doing this it is not only important to create this context up front but also update them while your project grows and evolves. I typically put it as an extra task at the end of each sprint.

Today when I opened VSCode, the following message popped up:

Wow! That’s great. Now it already starts suggesting bringing my copilot-instructions.md up to date for me!

In this example, it adds one rule to the file:

Sidenote: If you have a hard time coming up with good prompts, I recommend to certainly check out the Cursor rules examples. Although originally created for Cursor (another AI enabled IDE I really like), they can be a good starting point for your Copilot Instructions as well. 2 good websites to start with are:

CursorRules: AI Code Standards & .cursorrules Templates Hub

 

Cursor Directory

More information

GitHub Copilot - Custom Instructions

Custom instructions when using GitHub Copilot

GitHub Copilot– Reusable prompts files

Labels:

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         ...
Read more

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.
Read more

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’: ...
Read more