firebase-gcp-debug
Firebase + GCP Debug
Triage (always)
- Decide target: local emulators vs deployed (prod/staging)
- Identify
projectId(usually from.firebaserc/firebase.json) - Identify function/service name, region, and exact timestamp of the failure (UTC if possible)
- Collect the full error text + any request id / trace id
Local emulator workflow
- Confirm tooling versions:
node --versionfirebase --version
- Start only what you need (faster, less noise):
firebase emulators:start --only functions,firestore
- For Node debugging, enable inspector:
firebase emulators:start --only functions --inspect-functions
- Reproduce the issue and watch emulator logs.
More from xiaojiongqian/skills-hub
patent-search-cn-us
Patent prior-art search and novelty check guidance focused on China and the United States (CNIPA, USPTO, Google Patents, WIPO). Use when asked to plan or run CN/US patent searches, draft search strategies, or produce a preliminary novelty search report.
88jina-web-fetch
Fetch webpage text with a normal HTTP request first, then automatically fall back to jina.ai proxy when direct access fails or returns login/JS-blocked content. Use when extracting content from X (Twitter) or other pages that are hard to read directly.
52git-pr-merge
>
12gh-fix-ci
Inspect GitHub PR checks with gh, pull failing GitHub Actions logs, summarize failure context, then create a fix plan and implement after user approval. Use when a user asks to debug or fix failing PR CI/CD checks on GitHub Actions and wants a plan + code changes; for external checks (e.g., Buildkite), only report the details URL and mark them out of scope.
9auto-dev
>
8playwright-mcp
Use Playwright MCP for browser automation and regression checks when Chrome DevTools MCP is unavailable, when you need cross-browser coverage (Chromium/Firefox/WebKit), or when scripted browser control is more reliable.
7