database-design-quality-review
Use this skill when an ERD, DDL, ORM schema, or migration plan needs an evidence-bounded database design review before implementation; triggers include database design review, migration readiness review, and schema quality audit.
Install
npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/database-design-quality-review
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install naodeng-awesome-qa-skills@llmmart
git clone https://github.com/naodeng/awesome-qa-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole naodeng/awesome-qa-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Database Design Quality Review
Review ERDs, DDL, ORM schemas, data ownership, lifecycle, query constraints, transaction/concurrency, migration compatibility, and recovery design before implementation or migration. It produces DB-## findings and validation preparation; it does not connect to a real database or approve launch.
When to Use
- Use it to check model integrity, constraints, indexes, lifecycle/privacy, and data ownership.
- Use it to identify transaction, concurrency, migration rollback, backup/recovery, and performance risks.
- Use it when DDL or migration material is incomplete but a bounded design review is needed.
Do not use it to execute migrations, connect to production, benchmark queries, or infer business rules from table names.
Output Format Options
- Use Markdown by default; when a table, CSV, or JSON is requested, preserve the same evidence, status, impact, owner, and validation fields.
- Do not present a structured format or static inventory as execution, pass, approval, or release evidence.
How to Use
- Read this Skill's primary prompt and provide the objective, scope, material, environment, and available evidence.
- Follow the prompt's input audit and output contract; deliver a bounded first pass when information is incomplete.
- Retain source, evidence status, impact, owner role, close condition, and validation method for every finding.
Workflow
- Read
prompts/database-design-quality-review.mdand audit objective, version, database scope, and evidence. - Classify input as
known,missing,conflicting,stale,out_of_scope, andassumptions. - Build coverage by object, constraints, indexes, transaction/concurrency, lifecycle, migration, and recovery; bind evidence to
DB-##findings. - Separate facts, evidence-backed inferences, recommendations, and Human decisions with impact, owner, close condition, and validation.
- Without execution identity, time, environment, and raw results, do not write that a database operation succeeded.
Core Constraints
- Do not connect, write, migrate, or query a real database; do not run benchmarks or recovery drills.
- Do not infer business rules, thresholds, retention periods, or privacy classes from table or field names.
- Each
DB-##includes object, source/evidence, constraints/indexes, transaction/concurrency, migration rollback, impact, owner, and validation method. - All examples use redacted data; mark absent evidence
missing,unverified,unexecuted, orunassessed.
Reference Files
- Always read
prompts/database-design-quality-review.mdbefore producing a review. - For regression, read
evals/eval.yamland its cases; static design checks do not prove database behavior. - For trigger checks, use
evals/trigger-prompts.csvandevals/local-rules.json; missing selection trace isBLOCKED.
Best Practices
- Prioritize high-impact gaps with a verifiable next action, using the smallest useful experiment or evidence request.
- Separate facts, evidence-backed inferences, recommendations, and Human decisions; never upgrade an assumption into a conclusion.
Delivery Checklist
- Audit objects, version, ownership, scope, and evidence.
- Cover model, constraints, indexes, lifecycle/privacy, transactions, concurrency, migrations, performance, recovery, and test readiness.
- Give every
DB-##minimum evidence, impact, owner, action, and validation. - Use redacted examples and do not connect to a real database.
- Do not present DDL presence or static checks as migration success or launch approval.
Common Pitfalls
- Checking tables and fields without constraints, lifecycle, rollback, or recovery.
- Treating an index as proof that query performance was verified.
- Treating a parseable migration as backward compatibility and rollback proof.
Files (awesome-qa-skills)
-
agents
-
openai.yaml 433 B
Loading…
-
-
evals
-
cases
-
basic-success.yaml 1.1 KB
Loading… -
edge-incomplete-input.yaml 879 B
Loading… -
edge-scope-boundary.yaml 1.1 KB
Loading… -
review-online-mixed-version-migration.yaml 2.1 KB
Loading… -
review-valid-schema-control.yaml 1.6 KB
Loading…
-
-
eval.yaml 553 B
Loading… -
local-rules.json 141 B
Loading… -
trigger-prompts.csv 602 B · in bundle
-
-
prompts
-
database-design-quality-review.md 4.2 KB
Loading…
-
-
SKILL.md 4.3 KB
--- name: database-design-quality-review description: Use this skill when an ERD, DDL, ORM schema, or migration plan needs an evidence-bounded database design review before implementation; triggers include database design review, migration readiness review, and schema quality audit. license: PolyForm-Noncommercial-1.0.0 metadata: version: "1.0.0" compatibility: "" author: "Awesome QA Skills contributors" language: "en" category: "testing-types" source: "https://github.com/naodeng/awesome-qa-skills" license-url: "https://polyformproject.org/licenses/noncommercial/1.0.0" --- # Database Design Quality Review Review ERDs, DDL, ORM schemas, data ownership, lifecycle, query constraints, transaction/concurrency, migration compatibility, and recovery design before implementation or migration. It produces `DB-##` findings and validation preparation; it does not connect to a real database or approve launch. ## When to Use - Use it to check model integrity, constraints, indexes, lifecycle/privacy, and data ownership. - Use it to identify transaction, concurrency, migration rollback, backup/recovery, and performance risks. - Use it when DDL or migration material is incomplete but a bounded design review is needed. Do not use it to execute migrations, connect to production, benchmark queries, or infer business rules from table names. ## Output Format Options - Use Markdown by default; when a table, CSV, or JSON is requested, preserve the same evidence, status, impact, owner, and validation fields. - Do not present a structured format or static inventory as execution, pass, approval, or release evidence. ## How to Use 1. Read this Skill's primary prompt and provide the objective, scope, material, environment, and available evidence. 2. Follow the prompt's input audit and output contract; deliver a bounded first pass when information is incomplete. 3. Retain source, evidence status, impact, owner role, close condition, and validation method for every finding. ## Workflow 1. Read `prompts/database-design-quality-review.md` and audit objective, version, database scope, and evidence. 2. Classify input as `known`, `missing`, `conflicting`, `stale`, `out_of_scope`, and `assumptions`. 3. Build coverage by object, constraints, indexes, transaction/concurrency, lifecycle, migration, and recovery; bind evidence to `DB-##` findings. 4. Separate facts, evidence-backed inferences, recommendations, and Human decisions with impact, owner, close condition, and validation. 5. Without execution identity, time, environment, and raw results, do not write that a database operation succeeded. ## Core Constraints - Do not connect, write, migrate, or query a real database; do not run benchmarks or recovery drills. - Do not infer business rules, thresholds, retention periods, or privacy classes from table or field names. - Each `DB-##` includes object, source/evidence, constraints/indexes, transaction/concurrency, migration rollback, impact, owner, and validation method. - All examples use redacted data; mark absent evidence `missing`, `unverified`, `unexecuted`, or `unassessed`. ## Reference Files - Always read `prompts/database-design-quality-review.md` before producing a review. - For regression, read `evals/eval.yaml` and its cases; static design checks do not prove database behavior. - For trigger checks, use `evals/trigger-prompts.csv` and `evals/local-rules.json`; missing selection trace is `BLOCKED`. ## Best Practices - Prioritize high-impact gaps with a verifiable next action, using the smallest useful experiment or evidence request. - Separate facts, evidence-backed inferences, recommendations, and Human decisions; never upgrade an assumption into a conclusion. ## Delivery Checklist - [ ] Audit objects, version, ownership, scope, and evidence. - [ ] Cover model, constraints, indexes, lifecycle/privacy, transactions, concurrency, migrations, performance, recovery, and test readiness. - [ ] Give every `DB-##` minimum evidence, impact, owner, action, and validation. - [ ] Use redacted examples and do not connect to a real database. - [ ] Do not present DDL presence or static checks as migration success or launch approval. ## Common Pitfalls - Checking tables and fields without constraints, lifecycle, rollback, or recovery. - Treating an index as proof that query performance was verified. - Treating a parseable migration as backward compatibility and rollback proof.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.