This skill should be used when the user asks about build status in GCP, Google Cloud Build, or gcloud builds. Trigger phrases include "monitor the build", "watch the build", "check build status", "build in test environment", "build in staging", "build in production", "status of the build", "gcloud builds", "Cloud Build", "GCP build", "what happened with the build", "why did the build fail", "analyze the build failure", "did the build succeed", "check the deploy", "monitor the deploy", "anything weird with the build", or when user mentions checking CI/CD status in Google Cloud. Also use when user wants to use gcloud CLI to check build results or logs. Use proactively after merging a PR when build monitoring would be helpful.
From google-cloud-build-monitornpx claudepluginhub dhughes/claude-marketplace --plugin google-cloud-build-monitorThis skill uses the workspace's default tool permissions.
Monitor, analyze, and diagnose Google Cloud Build executions using the gcloud CLI. Provide continuous status updates until builds complete, with detailed failure analysis when builds fail.
Ensure the gcloud CLI is installed and authenticated:
gcloud auth list
gcloud config get-value project
If not authenticated, inform the user and provide authentication guidance.
Determine which GCP project contains the build:
Check current default project:
gcloud config get-value project
If context suggests a specific environment (staging, production, dev), look for matching projects:
gcloud projects list --format="table(projectId,name)" --filter="projectId~staging OR name~staging"
If multiple projects exist and the correct one is unclear, list available projects and ask the user:
gcloud projects list --format="table(projectId,name)"
Context clues for project selection:
Locate the specific build to monitor:
List recent builds:
gcloud builds list --project=PROJECT_ID --limit=10 --format="table(id,status,createTime,source.repoSource.branchName,substitutions.TRIGGER_NAME)"
Find in-progress builds:
gcloud builds list --project=PROJECT_ID --filter="status=WORKING OR status=QUEUED" --format="table(id,status,createTime,source.repoSource.branchName)"
Find builds by branch:
gcloud builds list --project=PROJECT_ID --filter="source.repoSource.branchName=BRANCH_NAME" --limit=5
Build identification strategy:
Retrieve comprehensive build information:
gcloud builds describe BUILD_ID --project=PROJECT_ID --format=json
Key fields to extract:
status: QUEUED, WORKING, SUCCESS, FAILURE, CANCELLED, TIMEOUTsteps: Array of build steps with individual statussource: Where the build came from (branch, commit, trigger)createTime, startTime, finishTime: Timing informationlogUrl: Link to Cloud Console logssubstitutions: Build variables including trigger namePolling behavior:
Progress updates:
Status interpretation:
QUEUED: Build waiting to start → continue pollingWORKING: Build in progress → continue pollingSUCCESS: Build completed successfully → announce completionFAILURE: Build failed → analyze failureCANCELLED: Build was cancelled → report cancellationTIMEOUT: Build exceeded time limit → report timeoutWhen a build fails, provide actionable diagnosis:
Identify failed step:
gcloud builds describe BUILD_ID --project=PROJECT_ID --format="json(steps)"
Parse the steps array to find which step has status: FAILURE.
Get step logs:
gcloud builds log BUILD_ID --project=PROJECT_ID --stream
For specific step logs, look at the log output around the failed step's execution time.
Failure analysis checklist:
Report format for failures:
❌ BUILD FAILED - PROJECT_ID
Build ID: BUILD_ID
Duration: X minutes
Failed Step: step-name (step N of M)
Error Summary:
[Extracted error message or description]
Log URL: [logUrl from build details]
Recommended Actions:
[Suggestions based on error type]
On success:
✅ BUILD SUCCEEDED - PROJECT_ID
Build ID: BUILD_ID
Duration: X minutes
Branch: branch-name
All steps completed successfully.
Audio announcement (macOS):
command -v say >/dev/null 2>&1
If say is available, announce completion with a human-friendly message:
say "Cloud Build for [branch or trigger name] completed successfully"say "Cloud Build for [branch or trigger name] failed"Important: Never include the build UUID in the spoken announcement—use the branch name, trigger name, or environment name instead for human-friendly audio.
When working in a GitHub PR context:
Find build from PR checks: If the PR has Cloud Build checks, the check details may include the build ID or a link to Cloud Console.
gh pr checks PR_NUMBER --json name,state,detailsUrl
Look for checks with "Cloud Build" in the name or detailsUrl pointing to console.cloud.google.com.
Find build from commit SHA:
gcloud builds list --project=PROJECT_ID --filter="substitutions.COMMIT_SHA=SHA" --limit=1
Authentication errors:
gcloud auth list for active accountgcloud auth login if neededPermission errors:
gcloud projects describe PROJECT_IDNetwork/API errors:
Offer to monitor builds in these situations:
Example: "I notice you just merged to main. Would you like me to monitor the production build?"
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.