cloud-run-deploy

Deploy repositories to Google Cloud Run using the project's existing deploy scripts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/lc0rp/luke-agent-scripts --skill cloud-run-deploy-lc0rp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-run-deploy
Source: https://github.com/lc0rp/luke-agent-scripts/tree/main/skills/cloud-run-deploy
Command: npx skills add https://github.com/lc0rp/luke-agent-scripts --skill cloud-run-deploy-lc0rp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploy a repository to Google Cloud Run using the project's own deploy flow, preferring existing scripts and live service configurations over ad hoc cloud commands.

Core Features & Use Cases

  • Deploy entrypoint discovery: Locates and uses repo-provided deploy helpers (e.g., scripts/deploy_cloudrun.py, npm run deploy:cloudrun, or make deploy) to perform Cloud Run deployments.
  • Live-service-aware: Extracts or infers target settings (region, project, service, runtime account, and env vars) from the current live Cloud Run service when docs do not specify them.
  • Verification & rollout readiness: Waits for build and rollout completion and reports deployment details such as the latest revision, service URL, and health status.

Quick Start

Run the repo's deploy entrypoint with the appropriate environment and verification steps to deploy the Cloud Run service.

Frequently Asked Questions about cloud-run-deploy

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

FAQPage Schema
How do I deploy a repository to Google Cloud Run using an existing deploy script?

To deploy a repository to Google Cloud Run safely, this approach locates and executes the project's predefined deploy entrypoint, such as scripts/deploy_cloudrun.py, npm run deploy:cloudrun, or make deploy, rather than running ad hoc gcloud commands. It automatically inspects repo docs to discover the correct deployment workflow.

How does Cloud Run deployment handle missing environment variables and service configuration?

When deploying to Cloud Run with missing configurations, the process extracts or infers necessary environment variables, service names, region, and runtime settings by inspecting the current live Cloud Run service. This ensures the new deployment matches existing live configurations.

Can I verify a Cloud Run deployment after pushing a new revision?

Yes, you can verify a Cloud Run deployment after rollout. The process waits for build and rollout completion, then reports deployment details including the latest revision, service URL, and health status to confirm the live service is running correctly.

What is the safest way to deploy to Google Cloud Run without breaking live service settings?

The safest way to deploy to Google Cloud Run is honoring the project's scripted deploy path and avoiding ad hoc cloud commands. This method discovers the repo's deploy entrypoint and extracts target settings from the live service to prevent configuration drift.

Does this Cloud Run deployment method work if my repo only uses a Makefile?

Yes, this Cloud Run deployment method works if your repo uses a Makefile. It supports discovering and executing standard deploy entrypoints like make deploy, alongside scripts/deploy_cloudrun.py or npm run deploy:cloudrun, to push the service.