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.
70
Quality
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Passed
No findings from the security scan
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
- Read change surfaces to identify all impacted layers
- Diagnose the bug across affected surfaces (runtime, CLI, UI, platform, tests)
- Implement coordinated fixes across all impacted surfaces
- Run
make agent-report ENV=cpu CHANGED_FILES="..."to verify all surfaces are accounted for - 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
- Repository
- vllm-project/semantic-router
- Commit
e73c772
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.