firebolt-db

Debug a failed E2E Tests GitHub Actions run for firebolt-kubernetes-operator by fetching job logs and the `e2e-report` artifact (e2e-report.xml, prepare-kind.log, run-e2e.log, pod-logs/) via the gh CLI, then correlating failed Ginkgo specs with pod logs and step output. Use when the user provides a GitHub Actions run URL or run ID for the E2E Tests workflow, or asks to investigate, triage, root-cause, or reproduce an E2E / Kind / Ginkgo failure from CI.

Author, release, and publish reusable GitHub Actions — including Docker container, JavaScript/TypeScript, and composite actions. Use this skill whenever the user wants to build a custom GitHub Action, author or edit an `action.yml`/`action.yaml`, wrap a CLI as a reusable action (`setup-$TOOL` pattern), handle action exit codes and failure behavior, tag and release an action with semantic versions, move or pin major-version tags (`v1`, `v2`), adopt immutable releases, publish to the GitHub Marketplace, or maintain an action over time. Trigger even when the user only implies action authoring — e.g. "I want to wrap our CLI so other repos can call it from workflows", "turn this script into something reusable in CI", "how do we share this step across repos", "set up a release pipeline for our action", "is our action's v1 tag moving correctly".