Mirrord Prev Env
Help users create and manage mirrord preview environments, running a modified service...
Install
npx skills add metalbear-co/mirrord --skill mirrord-prev-env -g -a claude-code -y- Repository
- metalbear-co/mirrord5.4k
- Category
- DevOps
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Help users create and manage mirrord preview environments, running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer wants to run "mirrord preview" ad hoc, share a preview via a link (mirrord-share-ingress), or wire preview environments into CI with the metalbear-co/mirrord-preview GitHub Action (e.g. per-PR previews, least-privilege cluster access).
Mirrord Preview Environment Skill
Purpose
Help users create and manage mirrord preview environments. A preview environment runs only the modified service(s) as isolated pods in a shared cluster, while their dependencies reach the rest of the main cluster through mirrord. Traffic is scoped by an environment key and a filter, so a change can be collaborated on, validated, and reviewed against real traffic without affecting live services.
This skill covers two modes:
- Ad-hoc (developer) mode, a developer runs the
mirrord previewCLI (start/status/stop) directly. - CI mode, the
metalbear-co/mirrord-previewGitHub Action wires previews into a PR lifecycle (start on open/push, stop on close).
When to Use This Skill
Trigger on questions like:
- "How do I run a mirrord preview environment?"
- "Set up per-PR preview environments with mirrord"
- "How do I use the mirrord-preview GitHub Action?"
- "
mirrord preview start, what config and flags do I need?" - "How do I route only my traffic to the preview pod?"
- "How do I check / stop a preview session?"
Security (must follow)
Preview environments deploy an image into a shared cluster and route live traffic to it, so the security bar is higher than for config generation. Always:
