Our review
This skill maintains a repository's GCP onboarding documentation, ensuring any changes to Google Cloud setup (OAuth, API scopes, Secret Manager, Cloud Run, environment variables) are reflected in the onboarding guides.
Strengths
- Centralizes critical GCP information in a single file, avoiding duplication.
- Promotes checklists and copy-paste commands for quick setup.
- Ensures configuration changes are documented consistently.
- Reduces risk of misconfiguration when onboarding new environments.
Limitations
- Requires manual updates and careful review after each change.
- May become outdated if changes are not documented promptly.
- Only covers documentation, not actual infrastructure configuration.
Use this skill when making changes to GCP components (OAuth, APIs, Secret Manager, Cloud Run, environment variables) and need to update the corresponding onboarding documentation.
Do not use for purely frontend or backend changes that don't affect GCP configuration, or for internal changes that don't require an onboarding documentation update.
Security analysis
SafeThe skill only instructs to maintain documentation files; it does not execute any commands, access external resources, or handle sensitive data. No executable tool usage is involved, and it explicitly warns against including secrets. Thus, it poses no security risk.
No concerns found
Examples
I've added a new OAuth scope for Google Calendar API in the backend. Please update the GCP onboarding documentation to reflect this new scope, including the consent screen and any changes to environment variables.We changed the Cloud Run service name from 'my-service' to 'new-service'. Update the onboarding guide with the new deployment commands and any configuration changes (e.g., memory, concurrency).We added a new secret called 'API_KEY' in Secret Manager for the backend. Update the onboarding docs to include instructions for granting access, referencing the secret, and setting the corresponding environment variable.name: gcp-onboarding description: Maintain this repository's GCP onboarding documentation. Use when changes touch Google Cloud setup, OAuth consent or clients, Google API scopes, Secret Manager, Cloud Run, GitHub Pages deployment configuration, backend environment variables, or frontend environment flags that a new project/environment must configure.
GCP Onboarding
When implementing changes that affect environment setup, inspect and maintain:
docs/guidelines/gcp-onboarding.mdprojects/frontend/README.mdprojects/backend/README.md.github/copilot-instructions.md
Keep onboarding docs concise and task-oriented. Prefer checklists, exact config names, and copy-pasteable commands. Avoid duplicating the full guide in multiple READMEs; link to docs/guidelines/gcp-onboarding.md from local setup sections.
Required checks:
- If OAuth origins, scopes, consent screen requirements, Google APIs, environment flags, secrets, Cloud Run settings, or deployment commands changed, update
docs/guidelines/gcp-onboarding.md. - If the setup change is not straightforward enough to document safely, add a short note in the PR or implementation summary that onboarding docs need confirmation.
- Keep existing documentation and links intact unless they are stale.
- Never include real secrets, private client secrets, or production-only secret values in documentation.
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Hono Documentation Search
Documentation
Use the hono CLI to search and view Hono framework documentation. It provides commands like hono search and hono docs to quickly find and browse documentation directly from the terminal. This is useful when developing with Hono and needing instant access to API references or guides.