google-cloud-run-ops

Deploy and operate Google Cloud Run services via repository-driven workflows and Cloud Build CI/CD.

1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Mrjoel97/PIKAR-AI --skill google-cloud-run-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: google-cloud-run-ops
Source: https://github.com/Mrjoel97/PIKAR-AI/tree/main/skills/google-cloud-run-ops
Command: npx skills add https://github.com/Mrjoel97/PIKAR-AI --skill google-cloud-run-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes uncertainty and manual guesswork when deploying, observing, and remediating Google Cloud Run services by providing a safe, inspect-first operational workflow tailored to repository-driven deployments and CI/CD pipelines.

Core Features & Use Cases

  • Deploy with repository intent: Prefer existing deploy scripts, make deploy, or Cloud Build triggers rather than inventing ad-hoc commands.
  • Inspect and diagnose: Walk through Cloud Run service state, revisions, Cloud Build history, and logs to identify build failures, crashes, auth errors, or config drift.
  • Safe maintenance and rollback: Recommend Terraform changes for codified infra, one-off Cloud Run mitigations for urgent fixes, and traffic-shift rollbacks to known-good revisions.
  • Repository-aware checks: Apply repository-specific guidance from the deploy map and runbook to validate secrets, Supabase and Redis connectivity, and WORKFLOW_SERVICE_SECRET alignment.

Quick Start

Deploy the repository using its preferred method (for example run the project's deploy entrypoint or trigger the appropriate Cloud Build), then inspect Cloud Run service details, recent builds, and logs and report project, region, service, revision, evidence, current status, and next steps.

Frequently Asked Questions about google-cloud-run-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy to Cloud Run using Cloud Build triggers from a repository?

To deploy to Cloud Run, trigger the repository's preferred Cloud Build pipeline or deploy entrypoint rather than inventing ad-hoc commands. The workflow inspects Cloud Build history and Artifact Registry state to ensure the deployment aligns with repository-specific intent.

Why is my Cloud Run service crashing after a deployment?

Cloud Run crashes are diagnosed by inspecting service state, recent revisions, and logs to identify auth errors, config drift, or missing secrets. The workflow validates Secret Manager settings and connectivity to dependencies like Supabase and Redis to pinpoint the root cause.

What's the best way to roll back a failed Cloud Run deployment?

The best way to roll back a failed Cloud Run deployment is a traffic-shift to a known-good revision. For codified infrastructure, Terraform changes are recommended, while one-off Cloud Run mitigations can address urgent fixes safely.

Do I need Terraform to manage Cloud Run infrastructure changes?

Terraform is recommended for codified infrastructure changes to Cloud Run, but not strictly required for urgent fixes. One-off Cloud Run mitigations can be applied directly, though Terraform ensures changes are tracked and reproducible.

How does repository-aware deployment work with Cloud Run?

Repository-aware deployment applies repository-specific guidance from the deploy map and runbook to validate secrets, connectivity, and WORKFLOW_SERVICE_SECRET alignment. It ensures deployments use existing scripts or Cloud Build triggers rather than ad-hoc commands.

Can I troubleshoot Cloud Build failures without direct Cloud Run access?

Troubleshooting Cloud Build failures requires gcloud access, project and region identifiers, and visibility into Cloud Build and Artifact Registry state. Permissions to inspect Cloud Run, IAM, and Secret Manager settings are also needed to identify build failures and config drift.