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

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

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

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