convex-deploy-guard

Classifies and announces the target Convex deployment before running deployment-affecting commands.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/Tehzeeb07/CodeRush --skill convex-deploy-guard-tehzeeb07
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: convex-deploy-guard
Source: https://github.com/Tehzeeb07/CodeRush/tree/main/.agents/skills/convex-deploy-guard
Command: npx skills add https://github.com/Tehzeeb07/CodeRush --skill convex-deploy-guard-tehzeeb07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Convex projects span multiple deployments (local, dev, preview, prod), and commands aimed at the wrong target cause silent failures or accidental production changes. This Skill enforces a discipline of identifying and announcing the deployment target before any deployment-affecting command runs. ## Core Features & Use Cases - Target Classification: Reads CONVEX_DEPLOYMENT, convex.json, and CONVEX_DEPLOY_KEY (or the Convex MCP status tool) to classify the target as local-anonymous, dev, preview, or prod. - Prod Consent Gating: Requires a fresh, explicit, per-session confirmation before prod deploys, prod env changes, snapshot import/export, or prod-scoped MCP access. - MCP Safety Defaults: Starts the Convex MCP scoped to non-prod and keeps the read-only prod flag separate from the mutating prod flag. - Use Case: Before running npx convex deploy, the agent announces target: dev (joyful-capybara-123, personal dev) and only proceeds after confirming the intended deployment, preventing accidental prod mutations. ## Quick Start Before running any Convex deploy or env command, identify and announce which deployment it will target, and ask for my explicit confirmation if it is production.

Frequently Asked Questions about convex-deploy-guard

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

FAQPage Schema
How do I avoid deploying to the wrong Convex deployment?▼

Identify the target before acting by reading CONVEX_DEPLOYMENT in .env.local, convex.json, and whether CONVEX_DEPLOY_KEY is set, or call the Convex MCP status tool. Announce the classified target in one line before running any deployment-affecting command.

How to safely run npx convex deploy against production?▼

State exactly what will change on which production deployment and get a fresh explicit yes in the current session before running the command. Consent given earlier or for a different target does not carry over.

What is the difference between the Convex MCP production flags?▼

--cautiously-allow-production-pii enables read-only prod tools for audits, while --dangerously-enable-production-deployments enables mutating prod tools. Keep them split: use the read-only flag for audits and the mutating flag only when the user explicitly asks to change prod.

Why did my Convex deploy not change anything?▼

The deploy almost certainly landed on a different deployment than the one being observed. Re-check the target via the status tool or compare npx convex env list fingerprints instead of re-running the deploy.

Can I enforce a read-only Convex session?▼

Yes. When the user requests read-only mode, honor it for the rest of the session: no deploys, no env set/remove, no mutations via run, and no imports. Start the MCP with --disable-tools run,envSet,envRemove.