convex-launch-readiness

Aggregates Convex audit findings into one scored, deduplicated launch-readiness report with an ordered fix plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before shipping a Convex backend, teams run separate authz, code-review, performance, and log audits and end up with four disconnected reports, duplicated findings, and no clear priority order. This Skill composes all audit passes into a single scored readiness report with a deduplicated, ranked fix plan. ## Core Features & Use Cases - Composed audit passes: Runs convex-authz, convex-reviewer, convex-advisor, and convex-insights, skipping passes whose preconditions (deployment, traffic) are unmet and stating what was skipped. - Auditable scoring: Starts at 100 and subtracts per confirmed finding by severity (high −15, med −5, low −1), printing the exact formula and per-class breakdown; plausible-only findings never move the score. - Deduped findings with fix dispatch: Normalizes each finding to a function/table identity so the same defect seen from code and deployment loci collapses to one, then dispatches accepted fixes to the owning fixer capability and re-runs passes to show the score delta. - Use Case: Before promoting a Convex app to production, run the readiness report to get a score, a blockers/should-fix/nice-to-have breakdown, and an ordered plan of which fixer capabilities to invoke next. ## Quick Start Run a launch-readiness report on my Convex backend and give me the score with an ordered fix plan.

Frequently Asked Questions about convex-launch-readiness

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

FAQPage Schema
How do I check if my Convex backend is ready for production?▼

Run a launch-readiness report that composes the authz scan, code reviewer, live-traffic advisor, and log insights into one scored report. It ranks findings by severity and ends with an ordered fix plan naming which fixer capability to run next.

How is the Convex readiness score calculated?▼

The score starts at 100 and subtracts per confirmed finding by severity: high −15, medium −5, low −1, floored at 0. The exact formula and per-class breakdown are printed, and plausible-only findings are listed as candidates without moving the score.

Does the readiness report work without a deployed Convex deployment?▼

Yes, but it produces a code-only score that is explicitly labeled as such. Passes requiring a live deployment or traffic, like the advisor and insights passes, are recorded as skipped rather than treated as clean results.

How are duplicate findings from different Convex audits handled?▼

Each finding is normalized to a function/table identity so the same defect reported from a code locus and a deployment locus collapses into one via (class, identity) dedup. The higher-confidence source is kept and nothing is dropped silently.

Does the readiness report fix the issues it finds?▼

No, it only decides what to fix and in what order. Each finding names a fixCapability, and on request the report dispatches accepted fixes to those fixer capabilities, then re-runs affected passes to show the score delta.