Review Your Bot

After VibeCoord generates your bot, you can review the code and see what commands were created before deploying.

Reviewing Generated Code

When generation completes, you’ll see the generated files in the Files panel (click the 📁 icon in the header).

What to Look For

• Command names — Check commands/ folder for slash command files
• Event handlers — Look for events/ folder for welcome messages, moderation triggers, etc.
• Configuration — The config/ folder contains bot settings

---

Understanding Your Bot

View the Code

1. Click the 📁 Files button in the header
2. Browse the generated project structure
3. Click any file to see its contents

Check Command Names

Commands are in the commands/ folder. Each file typically defines one slash command:

• commands/help.js → /help
• commands/joke.js → /joke
• commands/ban.js → /ban

---

Making Changes Before Deploy

If something isn’t quite right, simply tell VibeCoord in the chat:

“Add a /ping command that shows the bot’s latency”

“Change the welcome message to say ‘Hello friend!’”

“Remove the /kick command”

VibeCoord will update the code and you can review the changes.

---

Testing After Deployment

Currently, VibeCoord doesn’t have a sandbox preview environment. To test your bot:

1. Deploy to a test server — Create a private Discord server for testing
2. Add your bot — Deploy and add it to your test server
3. Try your commands — Test everything in a safe environment
4. Iterate — Make changes via chat and redeploy

Use a test server

Create a private Discord server with just you (and maybe a friend) for testing. This way you can safely test moderation commands without affecting real users.

---

Quick Testing Workflow

1. Generate your bot
2. Review the code in the Files panel
3. Deploy to your test server
4. Test commands in Discord
5. Iterate — tell VibeCoord what to change
6. Redeploy when satisfied

---

Ready to Deploy?

Once you’ve reviewed the generated code:

Set up deployment →