Stats
Actions
Tags
From Claude DB
Runs a read-only database audit and maps findings onto a production-readiness GO/NO-GO checklist (PITR, RLS, FK indexes, money-as-numeric, timestamptz/UTC, connection pooling, migration reversibility, secrets, charset).
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-db:checklist <path|connection-target> [--tier 0|1|2]<path|connection-target> [--tier 0|1|2]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
A **production-readiness GO/NO-GO** grid. **Read-only** — runs an audit and maps the findings onto a fixed launch checklist; never writes files or mutates the database.
A production-readiness GO/NO-GO grid. Read-only — runs an audit and maps the findings onto a fixed launch checklist; never writes files or mutates the database.
$ARGUMENTS = <path|connection-target> [flags]. The target is a repo path (schema/ORM/migration files) and, optionally, a live database via $DATABASE_URL for Tier-1/2 verification. If no target is given and no artifacts are found, say so and suggest /claude-db:start or /claude-db:design.
Invoke the db-orchestrator skill with the target and --tier flag to run the read-only audit (stack detection → schema parse → auditor subagents → merged findings → scores). Reuse an existing findings.json if the user passes one.
Map the merged findings onto the fixed checklist below. Each row gets a status — PASS (satisfied), WARN (non-blocking gap), FAIL (blocking gap), or NEEDS-LIVE (cannot be confirmed without a live connection / higher tier) — plus the finding id(s) that drive it.
| Check | What it verifies |
|---|---|
| PITR / backups | Point-in-time recovery or backup policy is configured — NEEDS-LIVE by default 1 |
| RLS on tenant tables | Row-level security enforced on multi-tenant tables |
| FK indexes | Every foreign key column is covered by an index |
| Money as numeric | Monetary columns use numeric/decimal, never float |
| timestamptz / UTC | Timestamps are timezone-aware and stored in UTC |
| Connection pooling sized | Pool is configured and sized for the platform's limits |
| Migration reversibility | Migrations have working down/rollback paths |
| Secrets not in schema | No credentials/secrets embedded in schema or DDL |
| charset / utf8mb4 | MySQL uses utf8mb4 (full Unicode), correct collation |
Render the grid as a table (Check · Status · Finding id · one-line note). Mark NEEDS-LIVE rows distinctly and state the tier needed to resolve them. Checks not applicable to the detected engine/paradigm (e.g. RLS or utf8mb4 on a non-relational store) are shown as N/A with a reason — never a silent pass.
Lead with a plain-language verdict at the top: GO (no FAILs), GO WITH CAVEATS (WARNs/NEEDS-LIVE only), or NO-GO (one or more FAILs) — one sentence on the headline blocker.
End by offering: "Run /claude-db:fix to apply the safe, reversible fixes, or /claude-db:next to see what to tackle first." Read-only throughout. Respond in the user's language (EN/ES).
No static module audits backups/DR/PITR, so this row is rendered NEEDS-LIVE by default — it can only be confirmed at Tier-1 (a live connection / provider config) and offline is reported as needs_api, never assumed present (never a silent PASS). ↩
npx claudepluginhub hainrixz/claude-db --plugin claude-dbProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Searches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.