cross-stack-bugfix

Diagnoses and fixes bugs spanning multiple layers with coordinated changes.

5.1k|806|Updated Aug 26, 2025
One-click install
npx skills add https://github.com/vllm-project/semantic-router --skill cross-stack-bugfix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-stack-bugfix
Source: https://github.com/vllm-project/semantic-router/tree/main/tools/agent/skills/cross-stack-bugfix
Command: npx skills add https://github.com/vllm-project/semantic-router --skill cross-stack-bugfix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses and fixes bugs that span multiple layers (runtime, CLI, UI, platform, and tests) requiring coordinated changes across surfaces.

Core Features & Use Cases

  • Cross-surface diagnosis across runtime, CLI, UI, platform, and tests
  • Coordinated fixes that apply across surfaces with validation
  • Use case: Resolve a regression that touches multiple layers and release a coordinated patch

Quick Start

Diagnose the cross-surface bug and implement coordinated fixes across runtime, CLI, UI, platform, and tests.

Frequently Asked Questions about cross-stack-bugfix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a bug that spans multiple layers like runtime, CLI, and UI?

Fix a bug spanning runtime, CLI, and UI layers by diagnosing across all affected surfaces and implementing coordinated changes. This cross-surface bugfix workflow reads change surfaces, applies coordinated fixes, and runs agent-report validation to verify the patch.

When do I need cross-stack bugfix coordination instead of a targeted patch?

You need cross-stack bugfix coordination when a regression touches multiple surfaces requiring cross-cutting validation, or when the issue does not map to a narrower single-layer fix and demands coordinated changes across runtime, CLI, UI, platform, and tests.

What is the workflow for diagnosing cross-surface regressions across platform and tests?

Diagnosing cross-surface regressions involves reading change surfaces, diagnosing across runtime, CLI, UI, platform, and tests, implementing coordinated fixes, and running agent-report to verify. Any remaining mismatches after validation are captured as technical debt.

Can I use this coordinated bugfix approach for single-layer runtime issues?

This coordinated bugfix approach applies when a bug touches more than one surface and requires cross-cutting validation. If the issue maps to a narrower single-layer fix without affecting runtime, CLI, UI, platform, and tests, a targeted skill is more appropriate.

What happens to remaining mismatches after a multi-layer bug fix?

Remaining mismatches after a multi-layer bug fix are captured as debt. The workflow enforces running agent-report to verify the coordinated fixes across runtime, CLI, UI, platform, and tests, ensuring any unresolved cross-surface issues are formally tracked.