triage-issue
Use when triaging a GitHub issue - analyzes issue, checks for duplicates, categorizes, and drafts response
Use when triaging a GitHub issue - analyzes issue, checks for duplicates, categorizes, and drafts response
Tool-calling pipeline with cost metering and approval workflows
Builds Docker images, starts local servers, and runs smoke tests for the AMD/ROCm development environment. Use when validating changes locally on AMD hardware, building AMD container images, or running AMD-specific smoke and explicit runtime checks.
Builds Docker images, starts local servers, and runs smoke tests for the CPU-only development environment. Use when validating changes locally on CPU, building CPU container images, or running CPU-specific smoke and E2E tests.
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/.
Modifies the fleet simulator package, API surface, release workflow, and simulator-owned docs or assets. Use when a primary skill touches src/fleet-sim or the simulator subsystem's owned website/release surfaces.
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.
Maintains Kubernetes-facing operator, deployment-profile, and DSL translation implementation slices for semantic-router platform integration. Use when the task changes operator APIs or CRDs, deployment manifests, profile-owned stack resources, or router-to-Kubernetes translation behavior.
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.
Implements end-to-end signal changes spanning router config, signal extraction, CLI schema, optional bindings, router-owned metadata headers, and E2E test coverage. Use when adding a new signal type, changing signal configuration or extraction logic, updating CLI schema for signal parameters, or modifying router-owned signal metadata contracts.
Research-to-implement pipeline chaining 5 MCP tools with graceful degradation
Update the body of a GitHub pull request. Use when the user asks to update, edit, or modify a PR description/body.
Search GitHub code, repositories, issues, and PRs via MCP
Generate comprehensive PR descriptions following repository templates
Use this skill to build, implement, and test Vizro dashboards (Phase 2). Activate when the user wants to create a working app, says "just build it", or has data ready for implementation. Requires spec files from the dashboard-design skill (Phase 1), or user confirmation to skip design.
Add a new configuration field to the Datadog Agent (datadog.yaml)
Run Erigon CI checks locally and/or trigger them remotely on a branch via GitHub Actions workflow_dispatch. Use this when you need to verify a branch passes all CI before or after pushing — especially for branches like bal-devnet-2 that don't auto-trigger on push/PR events.
Run Erigon Hive simulator tests locally or via GitHub Actions. Tests EL/CL protocol interoperability (engine API, RPC compat, EEST fixtures). Requires Docker and either `act` (for CI simulation) or direct hive invocation.