router-service-platform-change
$
npx mdskill add vllm-project/semantic-router/router-service-platform-change- Change router-side API, service, storage, provider, or support modules outside config, decision, selection, and extproc plugin chains - Change apiserver, authz, rate-limit, memory, response API, storage, or provider-adapter behavior
SKILL.md
.github/skills/router-service-platform-changeView on GitHub ↗
--- name: router-service-platform-change category: primary description: Modifies 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. --- # Router Service Platform Change ## Trigger - Change router-side API, service, storage, provider, or support modules outside config, decision, selection, and extproc plugin chains - Change apiserver, authz, rate-limit, memory, response API, storage, or provider-adapter behavior ## Workflow 1. Read change surfaces and module boundaries for the affected service layer 2. Modify the router-side service or API seam and identify whether profile-owned behavior changed 3. Run `make agent-report ENV=cpu CHANGED_FILES="..."` to verify surface alignment 4. Run `make agent-ci-gate CHANGED_FILES="..."` to validate the affected constraints 5. Update any impacted local or CI E2E expectation when the changed module is profile-owned ## Gotchas - These modules are not generic fallback territory anymore; if the change is in this surface, keep the service contract explicit instead of hand-waving it as cross-stack glue. - Storage, authz, and API seams often look local in code but still change E2E behavior through response-api, memory, or authz-rbac profiles. ## Must Read - [docs/agent/change-surfaces.md](../../../../docs/agent/change-surfaces.md) - [docs/agent/module-boundaries.md](../../../../docs/agent/module-boundaries.md) - [docs/agent/testing-strategy.md](../../../../docs/agent/testing-strategy.md) ## Standard Commands - `make agent-report ENV=cpu CHANGED_FILES="..."` - `make agent-ci-gate CHANGED_FILES="..."` - `make agent-feature-gate ENV=cpu CHANGED_FILES="..."` ## Acceptance - Router-side service modules, API seams, and affected validation paths stay aligned - Profile-owned behavior changes update the relevant local or CI E2E expectation
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.
- fleet-sim-changeModifies 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/.
- 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.