fleet-sim-change
$
npx mdskill add vllm-project/semantic-router/fleet-sim-change- Change the fleet simulator package, API service, CLI entrypoints, or release workflow - Change simulator-owned docs or static assets that must stay aligned with the maintained subsystem
SKILL.md
.github/skills/fleet-sim-changeView on GitHub ↗
--- name: fleet-sim-change category: primary description: Modifies the fleet simulator package, API service, release wiring, or simulator-owned docs and assets as one maintained subsystem. Use when changing src/fleet-sim, simulator release workflow, or fleet-sim-owned docs and assets under website/. --- # Fleet Sim Change ## Trigger - Change the fleet simulator package, API service, CLI entrypoints, or release workflow - Change simulator-owned docs or static assets that must stay aligned with the maintained subsystem ## Workflow 1. Read the fleet-sim local rules and change-surface contract 2. Modify the simulator package, workflow, or owned docs and assets as one subsystem 3. Run `make agent-report ENV=cpu CHANGED_FILES="..."` to verify routing and validation scope 4. Run the simulator validation path and any affected harness checks 5. Confirm simulator runtime and owned docs or assets still describe the same maintained surface ## Gotchas - `src/fleet-sim/**` is a first-class subsystem now; do not route it through generic fallback reasoning or treat its docs as repo-generic prose. - Moves inside `fleet_sim` still require public import and entrypoint stability, even when the visible change looks like a small API-handler edit. ## Must Read - [src/fleet-sim/AGENTS.md](../../../../src/fleet-sim/AGENTS.md) - [docs/agent/change-surfaces.md](../../../../docs/agent/change-surfaces.md) - [docs/agent/repo-map.md](../../../../docs/agent/repo-map.md) ## Standard Commands - `make agent-report ENV=cpu CHANGED_FILES="..."` - `make vllm-sr-sim-test` - `make agent-ci-gate CHANGED_FILES="..."` ## Acceptance - Simulator package, API entrypoints, and owned docs or assets stay aligned - Simulator release or runtime contract changes update the maintained workflow and validation path
More from vllm-project/semantic-router
- config-platform-changeSynchronizes config representations across router config, Python CLI schema, and dashboard config UI. Use when adding or changing a config concept that spans those surfaces or addressing config representation debt before Kubernetes-facing translation.
- cross-stack-bugfixDiagnoses and fixes bugs that span multiple layers (runtime, CLI, UI, platform, tests) requiring coordinated changes across surfaces. Use when a bug does not map cleanly to a narrower skill, the fix touches more than one surface, or changes need cross-cutting validation.
- dashboard-platform-changeModifies dashboard frontend or backend surfaces that present, configure, or manage router behavior through the console UI. Use when changing dashboard pages or components, backend handlers, console persistence, auth or session flows, or user-visible routing metadata in the dashboard.
- harness-contract-changeModifies the repository's agent contract including AGENTS.md, docs index, manifests, validation scripts, and contributor-facing harness wrappers. Use when updating agent documentation, changing repo manifests, editing validation scripts, modifying CI/workflow classification, or updating contributor-facing guides like README.md, CONTRIBUTING.md, or the PR template.
- k8s-platform-changeModifies Kubernetes-facing operator, CRD, deployment-profile, or DSL translation behavior for semantic-router platform integration. Use when changing operator APIs or controllers, deployment stack manifests, profile-owned platform wiring, or router-to-Kubernetes translation layers.
- maintainer-issue-pr-managementManages GitHub issue and pull-request lifecycle including creation, updates, triage labelling, and closeout metadata using canonical templates and repository taxonomy. Use when a maintainer asks to create, update, close, or triage GitHub issues or PRs, or when issue creation requires codebase analysis for scope, labels, or acceptance criteria.
- maintainer-release-opsMaintainer release and milestone operating workflow. Use when a maintainer wants to plan a release, create milestone issues, sync GitHub issue or PR state, generate a daily review brief, or manage stale PRs and backlog routing.
- openclaw-vsr-bridgeInstall vLLM Semantic Router in agent-safe mode, import supported OpenClaw model providers into canonical VSR config, and rewrite OpenClaw to target VSR.
- plugin-end-to-endImplements end-to-end plugin changes spanning router config, post-decision processing, optional CLI/UI exposure, and E2E test coverage. Use when adding a new plugin type, changing plugin config schema or execution semantics, updating plugin chain behavior, or modifying plugin-exposed metadata across surfaces.
- router-service-platform-changeModifies router-side API, authz, memory, provider, storage, or runtime service modules outside config, decision, selection, and extproc plugin chains. Use when changing apiserver endpoints, authz or rate-limit policy code, memory or response storage flows, provider adapters, or other router service-platform modules.