Maestro discord cli documentation#15
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 52 minutes and 6 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📝 WalkthroughWalkthroughAdded detailed README prerequisites documenting how to install and expose two CLIs: Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
scriptease
force-pushed
the
Maestro-Discord-CLI-documentation
branch
from
824534a to
8cb6da7
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
README.md (1)
23-35: Split mixed-shell snippets into shell-specific code fences
bashblocks currently include PowerShell content, which is easy to mis-copy and fail. Consider separate fenced blocks per platform (bashfor macOS/Linux,powershellfor Windows) for safer copy/paste.Also applies to: 47-60
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@README.md` around lines 23 - 35, The README contains mixed-shell code fences: the bash blocks include macOS/Linux printf lines ('printf ... /usr/local/bin/maestro-cli') and a Windows PowerShell batch creation block (Out-File to create maestro-cli.cmd), which can be mis-copied; split these into separate fenced blocks — use ```bash for the macOS and Linux printf/shebang snippets (the node "/Applications/Maestro.app/Contents/Resources/maestro-cli.js" and node "/opt/Maestro/resources/maestro-cli.js" lines) and a separate ```powershell block for the Windows batch snippet that creates maestro-cli.cmd with Out-File — apply the same separation to the later similar section that contains the Windows PowerShell content.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@README.md`:
- Around line 30-35: The Windows PowerShell snippets write .cmd wrappers under
ProgramFiles which is typically not on the user PATH, causing maestro-cli /
maestro-discord to be uncallable; update the README to either write the wrapper
into a directory that is on PATH (e.g., use
$env:ProgramData\Maestro\maestro-cli.cmd or %USERPROFILE%\bin) or add explicit
instructions to add the created ProgramFiles\Maestro folder to PATH, and update
both the maestro-cli and maestro-discord snippets (the .cmd creation lines
shown) so the Out-File target is a PATH-accessible location or document the PATH
export step.
---
Nitpick comments:
In `@README.md`:
- Around line 23-35: The README contains mixed-shell code fences: the bash
blocks include macOS/Linux printf lines ('printf ...
/usr/local/bin/maestro-cli') and a Windows PowerShell batch creation block
(Out-File to create maestro-cli.cmd), which can be mis-copied; split these into
separate fenced blocks — use ```bash for the macOS and Linux printf/shebang
snippets (the node "/Applications/Maestro.app/Contents/Resources/maestro-cli.js"
and node "/opt/Maestro/resources/maestro-cli.js" lines) and a separate
```powershell block for the Windows batch snippet that creates maestro-cli.cmd
with Out-File — apply the same separation to the later similar section that
contains the Windows PowerShell content.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
|
The unit tests fail with missing token Error: Missing required env var: DISCORD_BOT_TOKENat required (/home/runner/work/Maestro-Discord/Maestro-Discord/dist/config.js:13:15)at Object. (/home/runner/work/Maestro-Discord/Maestro-Discord/dist/config.js:26:12)at Module._compile (node:internal/modules/cjs/loader:1705:14)at Object..js (node:internal/modules/cjs/loader:1838:10)at Module.load (node:internal/modules/cjs/loader:1441:32)at Function._load (node:internal/modules/cjs/loader:1263:12)at TracingChannel.traceSync (node:diagnostics_channel:328:14)at wrapModuleLoad (node:internal/modules/cjs/loader:237:24)at Module.require (node:internal/modules/cjs/loader:1463:12)at require (node:internal/modules/helpers:147:16) |
Add Linux, Windows, and direct Node.js install instructions for both maestro-cli and maestro-discord CLIs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
scriptease
force-pushed
the
Maestro-Discord-CLI-documentation
branch
from
5b75579 to
b61071e
Compare
- Remove the inline "Install Maestro CLI" section from the README and instead link to https://docs.runmaestro.ai/cli from the Prerequisites list, so install instructions live in one canonical place. - For the remaining maestro-discord install section, write the wrapper to %USERPROFILE%\bin (instead of %ProgramFiles%) and idempotently add that dir to user PATH so the wrapper is actually callable. - Split the mixed bash + PowerShell fenced blocks into separate bash and powershell blocks to prevent mis-copy and restore highlighting. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
scriptease
force-pushed
the
Maestro-Discord-CLI-documentation
branch
from
b61071e to
0a7147d
Compare
3 participants
Added discord cli installation documentation
Summary by CodeRabbit