Slash commands and @ files

When you would want it

Typing is faster than hunting for a button, and each command asks the way an experienced engineer would - including checking its own work - so answers come back verified rather than guessed.

Where to find it

• All Features → Slash commands and @ files
• Show commands
• Add a file

What you get out of it

• Common requests take two keystrokes, and each one asks for verification - tests run, typechecks pass - instead of an unchecked guess.
• /review reads the real diff from git, including staged work and newly added files, so nothing gets reviewed from memory.
• @ puts exactly the file you mean in front of the model, which saves a round of it searching for the wrong one.
• Your history stays readable: past conversations are titled with what you typed, like /review focus on auth, not with a paragraph of boilerplate.
• Commands that change code follow your edit approval: by default the edits land as the assistant works, and Undo in the chat takes any turn back.

How to use it, step by step

1. Open the Assistant (Ctrl+I) and type / at the start of the composer to see every command.
2. Keep typing to filter - /re finds /review and /refactor - then press Enter or Tab. Arrow keys move through the list; Esc closes it.
3. Choose /review to attach your uncommitted changes and get a bug-focused review with file and line, or /commit for a ready-to-use commit message. Both go as soon as you pick them; type /review focus on auth to say what to look at.
4. Choose /fix, /test, /plan, /refactor, /explain, /optimize, /security, /docs or /build, add your own details and send. On its own, a command is about the file you have open. /check asks the assistant to look at your running app in its own browser and fix what is broken.
5. Or skip the menu: type the command and your words together - /fix the login button does nothing - and press Enter. Your message shows as /fix plus your words, and the conversation is titled the same way, while the assistant receives the command's full, carefully worded instruction.
6. Action commands work typed too, even while an answer is being written: /model opens the model picker, /new followed by a message starts a fresh conversation and sends it, /team add a discount code to the cart sets up an AI Team for that task, and /compact keep the API decisions makes room while keeping what you name.
7. Type @ anywhere in a message to search your project's files. Pick one and it rides along as a chip; if it is open in the editor, its unsaved text is what gets sent.
8. In an empty composer, press the Up arrow to bring back what you sent before - handy for re-running a request after a fix.

Why this beats the usual way

Most chat panels make you type the same careful instructions again and again, or keep them in a notes file. Agentfly ships the good versions as commands, reads your diff for you, and lets you point at a file with @ instead of pasting it, so the prompt you send is the prompt an experienced engineer would write.

Find it in Universal Search

Slash commands and @ files · The assistant · slash commands · review my changes · commit message · write tests · mention a file · at mention · @file · prompt history · previous prompt