Conversation
…ment The CLI `context` command lets users set default project, environment, and service — avoiding repetitive --project-id and --id flags on every command. This is especially useful for LLM-driven workflows where brevity matters. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
WalkthroughAdds a new documentation page "Zeabur Context Management" that documents using the Zeabur CLI context to set default project, environment, and service identifiers, plus commands to set/get/clear context and a short usage workflow. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/zeabur-context/SKILL.md`:
- Line 23: Update the guidance in the zeabur-context SKILL.md to remove or
de-emphasize recommending `--name` as an alternative to `--id` so it matches the
reliability guidance in the zeabur-service-list SKILL.md; specifically, edit the
sentence that reads "Supports `--name` as alternative to `--id`" to either
remove `--name` from recommended usage or add a clear note that `--id` is
preferred and `--name` is unreliable, referencing the same operator guidance
used by the zeabur-service-list skill; ensure references to flags `--name` and
`--id` and the skill identifier "zeabur-context" are updated so the docs no
longer conflict.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 01ec3f86-da20-4ec2-9d6e-334d6c518c61
📒 Files selected for processing (1)
skills/zeabur-context/SKILL.md
Address CodeRabbit review: --name lookup is unreliable, align with the same guidance used in zeabur-service-list and zeabur-restart. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Summary
zeabur-contextskill covering the CLIcontextcommand (set,get,clear)--project-idand--idflags on subsequent commandsWhy this skill?
The
contextcommand exists in the CLI but none of the existing 25 skills mention it. Setting a default project is one of the first things users should do, and this gap means LLMs never suggest it.Test plan
context set project/env/service,context get,context clear) work on a real Zeabur accountproj,env,svc) and--nameflag workzeabur-restartfor reference)🤖 Generated with Claude Code
Summary by CodeRabbit