Skip to content

BrokenCode guide

Commands in BrokenCode

Use built-in slash commands and create reusable project commands with arguments, file references, and shell context.

UPDATED 03 Aug 20264 min readTECHNICAL GUIDE
01

Built-in commands keep the session moving.

Core commands
CommandPurpose
/initCreate or refresh project instructions
/undoUndo the latest reversible change
/redoRestore an undone change
/shareCreate a shareable session link
/helpOpen command and keybinding help
02

Store the prompt once; call it whenever you need it.

Create Markdown commands under .brokencode/commands for a project or ~/.config/brokencode/commands for every project.

.brokencode/commands/component.md

---
description: Create a typed UI component
agent: build
---
Create a React component named $ARGUMENTS. Match this project's conventions and add focused tests.
03

Commands can accept arguments and current context.

  • $ARGUMENTS expands to the full text after the command.
  • $1, $2, and later positions select individual arguments.
  • Use file references and shell-output blocks when a command needs concrete project evidence.

Run it

/component Button

STRAIGHT ANSWERS

Frequently asked questions

01Where do project commands live?

Use .brokencode/commands/*.md in the repository.

02Can one command use a particular agent?

Yes. Set agent in the command frontmatter or JSON configuration.

Install

Make your workflow executable.

Install BrokenCode and keep project commands beside the code they understand.

Get BrokenCode