startup-chain-change

Name: startup-chain-change
Author: vllm-project/semantic-router

$npx mdskill add vllm-project/semantic-router/startup-chain-change

Modifies local startup chain for image build, container serve/bootstrap logic, and canonical smoke test behavior

Identifies changes to `vllm-sr serve`, image selection, pull policy, or container startup behavior.
Deploys modifications through environment documentation and agent feature gates.
Automatically identifies impacted surfaces with a report command.
Validates startup behavior using an agent feature gate before deployment.

SKILL.md

.github/skills/startup-chain-changeView on GitHub ↗

---
name: startup-chain-change
category: primary
description: Modifies the local startup chain including image build, container serve/bootstrap logic, and canonical smoke test behavior. Use when changing `vllm-sr serve` behavior, image selection or pull policy, container startup sequences, local Docker/Make bootstrap, or canonical smoke config.
---

# Startup Chain Change

## Trigger

- Change `vllm-sr serve`, image selection, pull policy, or container startup behavior
- Change canonical local smoke config or agent smoke flow
- Change local Docker or Make bootstrap behavior

## Workflow

1. Read environment docs for startup chain context
2. Modify serve, bootstrap, image selection, or smoke config
3. Run `make agent-report ENV=cpu|amd CHANGED_FILES="..."` to identify impacted surfaces
4. Run `make agent-feature-gate ENV=cpu|amd CHANGED_FILES="..."` to validate startup behavior
5. Verify the canonical local serve path works with the default smoke config

## Gotchas

- Do not introduce an alternate local serve path; the local image flow remains the canonical local-dev contract.
- A smoke-only green run is not enough when CLI orchestration or image selection semantics changed.

## Must Read

- [docs/agent/environments.md](../../../../docs/agent/environments.md)
- [docs/agent/amd-local.md](../../../../docs/agent/amd-local.md)
- [docs/agent/testing-strategy.md](../../../../docs/agent/testing-strategy.md)

## Standard Commands

- `make agent-report ENV=cpu|amd CHANGED_FILES="..."`
- `make agent-feature-gate ENV=cpu|amd CHANGED_FILES="..."`

## Acceptance

- The canonical local serve path works with the default smoke config
- Startup-chain changes include local smoke plus relevant CLI or integration coverage

More from vllm-project/semantic-router

Skill	Description
config-platform-change	Synchronizes 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-bugfix	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.
dashboard-platform-change	Modifies 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-change	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/.
harness-contract-change	Modifies 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-change	Modifies 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-management	Manages 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-ops	Maintainer 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-bridge	Install 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-end	Implements 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.