otgruzka-deploy-auditor

Audits UI-only Vercel deployments and blocks Firestore data mutations during deploys.

Updated May 5, 2026
One-click install
npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill otgruzka-deploy-auditor-nikegeorgian-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: otgruzka-deploy-auditor
Source: https://github.com/nikegeorgian-stack/otgruzka-tovara/tree/main/.cursor/skills/otgruzka-deploy-auditor
Command: npx skills add https://github.com/nikegeorgian-stack/otgruzka-tovara --skill otgruzka-deploy-auditor-nikegeorgian-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying a web UI update can accidentally wipe or overwrite production Firestore data when agents run import, clear, or migration scripts alongside the deploy. This Skill enforces a strict audit checklist so a deploy is only declared done with verifiable proof and zero database side effects. ## Core Features & Use Cases - Pre-deploy checklist: Requires an explicit user request, a UI-only goal, a clean npx tsc --noEmit run, and the preferred npm run deploy:otgruzka:quick command. - Forbidden-action guard: Blocks clear:*, import:cloud*, clean:cloud-store:apply, migration scripts, non-hosting firebase deploy, .env swaps, and unprompted git push in the same session. - Post-deploy verification: Confirms exit code 0, fetches https://otgruzka-tovara.vercel.app to verify the new index-….js bundle hash, and issues a PASS/FAIL verdict stating Firestore was untouched. - Use Case: Before running npm run deploy:otgruzka:quick, the agent walks the checklist, refuses a bundled data-import request, deploys, verifies the bundle hash on the Vercel production URL, and reports DEPLOY AUDIT: PASS with the hash. ## Quick Start Ask the agent to audit the Otgruzka deploy before and after running npm run deploy:otgruzka:quick and confirm Firestore data was not touched.

Frequently Asked Questions about otgruzka-deploy-auditor

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

FAQPage Schema
How do I safely deploy a UI-only update to Vercel without touching Firestore?▼

Run the pre-deploy checklist: get an explicit deploy request, confirm the goal is UI-only, pass npx tsc --noEmit, then run npm run deploy:otgruzka:quick. Never combine the deploy with clear, import, or migration scripts in the same session.

How to verify a Vercel deployment actually published the new build?▼

Send an HTTP GET to the production URL https://otgruzka-tovara.vercel.app and check the HTML references the new index-….js bundle hash. Checking Firebase Hosting (web.app) is not valid because the canonical production target is Vercel.

What commands are forbidden during an Otgruzka deploy?▼

Forbidden commands include clear:*, import:cloud*, clean:cloud-store:apply, migrate:sql-connect, migrate:cloud-store, firebase deploy without --only hosting, swapping .env to another Firebase project, and git push without a separate explicit request.

Why did data disappear after a deploy?▼

Data loss typically happens when import or clear scripts ran alongside the deploy, overwriting Firestore with local JSON. The audit treats any Firestore mutation in the deploy session as a FAIL and requires reporting exactly what was touched.

Can the deploy guard hook be bypassed with a reworded script?▼

No. The audit explicitly forbids circumventing the otgruzka-deploy-guard hook through alternate script formulations with the same effect. If a user explicitly requests a clear or import, the agent must stop and confirm consequences before proceeding.