Skip to main content

Actions

actions

How to use it​

Actions are shortcuts for common use cases. For example, you might want to review code, write tests, or add a docstring.

Slash commands​

The most common way to invoke an action is with a slash command. These are shortcuts that can be activated by typing '/' and selecting from the dropdown. For example, the built-in '/edit' slash command lets you stream edits directly into your editor.

slash-commands

A few of the most useful slash commands are available by default, like “/edit”, “/comment”, and “/share”, but Continue has a large built-in library of other options. To enable these, learn more here.

Prompt files​

It is also possible to write your own slash command by defining a “.prompt file.” Prompt files can be as simple as a text file, but also include templating so that you can refer to files, URLs, highlighted code, and more.

The full .prompt file reference can be found here.

Prompt library

To assist you in getting started, we've curated a small library of .prompt files. We encourage community contributions to this repository, so please consider opening up a pull request with your own prompts!

Below is a quick example of setting up a prompt file to write unit tests using Jest.

  1. Create a folder called .prompts/ at the top level of your workspace.
  2. Add a file called test.prompt to this folder. The name of this file will be the name of the slash command you will use to generate your prompt.
  3. Write the following contents to test.prompt and save.
{{{ input }}}

Write unit tests for the above selected code, following each of these instructions:
- Use `jest`
- Properly set up and tear down
- Include important edge cases
- The tests should be complete and sophisticated
- Give the tests just as chat output, don't edit any file
- Don't explain how to set up `jest`

Now to use this prompt, you can highlight code and use cmd/ctrl+L to select it in the Continue sidebar.

Then, type "/" to see the list of slash commands and choose the one called "test". Press enter and the LLM will respond given the instructions from your prompt file.

Other triggers for Actions (VS Code)​

info

Currently all of these are only available in VS Code

To make common use cases even more accessible, we provide a handful of other ways to invoke actions.

Quick actions​

Quick Actions are displayed as buttons above top-level classes and functions in your source code, letting you invoke actions with one click. They can also be customized with .prompt files to perform custom actions.

quick-actions

By default, quick actions are disabled, but can be enabled with the “Continue: Enable Quick Actions” in VS Code settings.

Right click actions​

Right click actions let you highlight a desired region of code, right click, and then select an action from the dropdown menu.

context-menu

Debug action​

The debug action is a special built-in keyboard shortcut in the VS Code extension. Use cmd/ctrl+shift+R to instantly copy the contents of the current terminal into the chat sidebar and get debugging advice.

Quick fixes​

Whenever you see red/yellow underlines in your code indicating errors, you can place your cursor nearby and VS Code will display a lightbulb icon. Either clicking the lightbulb or using the keyboard shortcut cmd/ctrl+. will show a dropdown menu of quick fixes. One of these will be the “Ask Continue” action. Either click or use cmd/ctrl+. again and Continue will attempt to help solve the problem.

ask-continue