gcb-monitor_skill

Overview

This skill monitors Google Cloud Build executions and provides continuous status updates until builds complete. It uses the gcloud CLI to find builds, stream logs, and perform focused failure analysis. It reports progress, notifies on completion, and gives actionable remediation steps when builds fail.

How this skill works

It identifies the correct GCP project from context or explicit input, locates the target build (by ID, branch, trigger, or commit SHA), then polls gcloud builds describe every 60 seconds. While running it streams relevant logs, highlights step-level progress, and on failure extracts the failed step and error messages. It also integrates with GitHub PR checks to map PRs to Cloud Build runs.

When to use it

• After merging a PR to monitor the resulting CI build
• When a user asks “check build status” or “what happened with the build”
• Before or during deployments to staging or production
• When you want to use gcloud CLI to inspect build logs or results
• If a build is stuck in QUEUED or WORKING and you need step-level insight

Best practices

• Confirm or infer the correct GCP project before querying builds
• Prefer build ID when available; otherwise filter by branch, trigger, or commit SHA
• Poll every 60 seconds and report summary updates; give detailed logs on failures
• When diagnosing failures, identify the failed step, extract error messages, and link to the console log URL
• Use human-friendly names (branch or trigger) for spoken notifications; avoid mentioning UUIDs

Example use cases

• Monitor the production build after a merge to main and get notified on success or failure
• Watch a staging build for a hotfix and stream failing test output to triage quickly
• Investigate a failed deployment step by retrieving step logs and recommended fixes
• Map a GitHub PR check to a Cloud Build run and follow its logs until completion
• Continuously poll a long-running build and report step completions and final status