OpenParable
Skip to content
← Back to skills

Cross Stack Bugfix

Testing & Quality
cross-stack-bugfix

Cross Stack Bugfix is an Agent Skill for testing & quality published in the vllm-project/semantic-router repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

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/cross-stack-bugfix/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cross-stack-bugfix, 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.

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

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