cross-stack-bugfix
$
npx mdskill add vllm-project/semantic-router/cross-stack-bugfix- A bug spans multiple layers and no narrower primary skill clearly applies - The fix needs coordinated changes across runtime, CLI, UI, platform, or test surfaces
SKILL.md
.github/skills/cross-stack-bugfixView on GitHub ↗
--- name: cross-stack-bugfix category: primary description: Diagnoses 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. --- # Cross Stack Bugfix ## Trigger - A bug spans multiple layers and no narrower primary skill clearly applies - The fix needs coordinated changes across runtime, CLI, UI, platform, or test surfaces ## Workflow 1. Read change surfaces to identify all impacted layers 2. Diagnose the bug across affected surfaces (runtime, CLI, UI, platform, tests) 3. Implement coordinated fixes across all impacted surfaces 4. Run `make agent-report ENV=cpu CHANGED_FILES="..."` to verify all surfaces are accounted for 5. Promote any remaining mismatches into indexed debt entries ## Gotchas - Treat this as the fallback skill; if inspection shows a narrower primary skill fits, switch to that more specific contract. - Fixing the symptom in one layer is not enough when another touched surface still carries the underlying contract mismatch. ## Must Read - [docs/agent/change-surfaces.md](../../../../docs/agent/change-surfaces.md) ## Standard Commands - `make agent-report ENV=cpu CHANGED_FILES="..."` - `make agent-feature-gate ENV=cpu CHANGED_FILES="..."` ## Acceptance - The final report explicitly names impacted surfaces and intentionally skipped conditional surfaces - Any real code or spec mismatch left behind is promoted into the matching indexed debt entry
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.
- 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.
- 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.