Skip to main content

VSCode–Finetune your AI instructions with /init

If you're using GitHub Copilot in Visual Studio Code, there's a powerful new feature that can save you time and make your AI-powered development workflow more efficient: the /init command. This slash command provides a quick way to set up custom instructions for your workspace or adapt your existing instructions to the specific project context, helping you establish consistent coding practices and AI responses across your projects.

What is the /init command?

The /init command is a chat slash command in VSCode that helps you quickly prime your workspace with custom instructions for GitHub Copilot. When you type /init in the chat input box, it automatically generates a .github/copilot-instructions.md file tailored to your workspace.

Think of it as a quick-start wizard for setting up AI guidelines that will influence how Copilot generates code and handles development tasks throughout your project.

How to use the /init command?

Using the /init command is straightforward:

  1. Open the Chat view in VSCode (you can use the GitHub Copilot icon in the Activity Bar)
  2. In the chat input box, type /init
  3. Press Enter

That's it! VSCode will start analyzing your workspace and automatically generate a .github/copilot-instructions.md file with custom instructions that match your coding practices and project structure.


After the file is generated, you should:

  1. Review the generated instructions carefully
  2. Make any necessary edits to align with your specific needs
  3. Commit the file to your version control system to share with your team

The generation is done using a init.prompt.md file that you can customize further if you want. No magic here!

As mentioned in the intro, this also works when you already have a .github/copilot-instructions.md file in place. In that case the /init command will review the existing settings and adapt them where necessary.

Nice!

More information


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