name: convex-deploy-env-doctor description: Validate and fix Convex deployment configuration for skills/apps. Use when debugging Convex URL/callback/env issues, OAuth callback mismatches, .site vs .cloud confusion, or backend connectivity problems before publish/deploy. Do not use for non-Convex stacks. Success = clear pass/fail checks, exact fixes, and verified runtime URL consistency.

Convex Deploy + Env Doctor

Workflow

1. Detect project config surface
2. Check .env, .env.example, runtime defaults in source, README/SKILL docs.

3. Extract all Convex URLs and callback URLs.

4. Validate URL consistency

5. Ensure one canonical backend URL intent (.cloud for API by default).
6. Flag mixed .site/.cloud usage and explain where each is appropriate.

7. Ensure callback URLs match provider/app configuration.

8. Validate required env vars

9. Check required/optional env keys and whether docs match runtime usage.

10. Flag hidden defaults that route data unexpectedly.

11. Connectivity sanity check

12. Run lightweight checks (lint/build and safe HTTP reachability if possible).

13. Confirm configured backend is HTTPS and syntactically valid.

14. Output

15. Return:
16. ✅ Passing checks
17. ❌ Failing checks
18. exact file-level patches required
19. post-fix verification commands
20. explicit data-routing disclosure (what endpoints/services were touched)

Output format

Use references/output-template.md.

Guardrails

• Never print secrets.
• Prefer minimal patch release changes.
• Keep docs and runtime behavior aligned.
• Include file+line evidence for each failing check.