CodeNeterCommands
Save prompts you use often as slash commands and run them from the message box.
Commands turn prompts you send often into slash commands. Each command is a Markdown file; its file name becomes the command, and running it sends the file's contents to the agent.
Where commands live
| Scope | Folder |
|---|---|
| User | ~/.codeneter/commands/ |
| Project | .codeneter/commands/ in the project |
If a user command and a project command have the same name, the project command runs. You can also create and edit commands in the Rules + Skills + Commands settings.
Command format
The file name sets the command. review-branch.md becomes /review-branch. Names are lowercased, and spaces and other characters become hyphens, so Review Branch.md also becomes /review-branch.
---
description: Review the current branch before opening a pull request
---
Review the changes on this branch compared with main. Look for missing tests, unclear names, and changes to public APIs. List problems by file, most important first. Don't edit any files.Frontmatter is optional. It can set a description, or turn the command off with enabled: false.
Running a command
Type / in the message box and choose the command, or type its name. Anything you write after the command is sent along with it:
/review-branch focus on the authentication changesCommands don't have argument placeholders. Extra text is added after the command's instructions.