OpenParable
Skip to content
← Back to skills

Startup Chain Change

DevOps & Security
startup-chain-change

Startup Chain Change is an Agent Skill for devops & security published in the vllm-project/semantic-router repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/vllm-project/semantic-router/blob/HEAD/tools/agent/skills/startup-chain-change/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/startup-chain-change, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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

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