database-schema-reviewer
Skill0 starsChanged 19 days agoMITView on GitHub
Review relational or document schemas for keys, relationships, constraints, nullability, indexes, and access-pattern fit. Use before schema creation or migration.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- imohammadfaraz/claude-skills-for-product-managertheir own version, first seen Nov 1, 2026
- conectlens/lenserfighttheir own version, first seen May 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- imohammadfaraz/claude-skills-for-product-manager★ 19same name
- conectlens/lenserfight★ 18same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- completion-claims-auditorSkill
- existing-work-preservationSkill
- mcp-reliability-auditorSkill
- multi-agent-integration-reviewerSkill
- project-context-recoverySkill
- requirement-traceability-auditorSkill
- scope-drift-guardSkill
- architecture-complexity-auditorSkill
- dependency-cycle-auditorSkill
- data-consistency-auditorSkill
- migration-safety-reviewerSkill
- loop-breakerSkill
- reproduction-builderSkill
- root-cause-debuggerSkill
- dependency-grounding-auditorSkill
- ci-failure-investigatorSkill
- cross-platform-readiness-auditorSkill
- environment-config-auditorSkill
- environment-parity-auditorSkill
- production-readiness-auditorSkill
- documentation-accuracy-auditorSkill
- token-efficient-workflowSkill
- accessibility-auditorSkill
- dead-feature-detectorSkill
- responsive-design-auditorSkill
- ux-state-completeness-auditorSkill
- release-verification-agentSkill
- agent-tool-trust-auditorSkill
- authentication-security-auditorSkill
- authorization-boundary-auditorSkill
- dependency-vulnerability-auditorSkill
- injection-risk-auditorSkill
- input-validation-auditorSkill
- secret-leakage-detectorSkill
- security-misconfiguration-auditorSkill
- api-contract-auditorSkill
- integration-reality-checkerSkill
- missing-test-detectorSkill
- regression-detectorSkill
- test-quality-auditorSkill
- ui-flow-verifierSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Read applicable repository instructions before edits.
- Distinctive: line 33
Check relationship cardinality, ownership, foreign keys/references, cascade behavior, and orphan policy.
- Distinctive: line 34
Check nullability, uniqueness, checks/enums, defaults, timestamps/version fields, and server-generated identifiers against invariants.
- Distinctive: line 36
Check tenant/authorization scoping fields are representable and queryable where needed.
- Distinctive: line 46
Never run destructive schema experiments against production or irreplaceable data.
- Distinctive: line 63
If real access patterns or invariants are unknown, ask from existing product/spec evidence and mark unresolved design choices rather than …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Purpose
Make data invariants explicit in the storage layer where appropriate.
When to activate
A data model/schema/migration is introduced or changed.
When not to activate
An in-memory-only data structure has no persistence contract.
Preconditions
- Read applicable repository instructions before edits.
- Preserve unrelated working-tree changes and establish a baseline when the workflow can modify code.
- Identify which tools and environments are actually available; do not claim unavailable checks ran.
Required inputs
- Schema/models/migrations
- Primary queries and write flows
- Business invariants
Workflow
- List entities/collections and the identities used to address them.
- Check relationship cardinality, ownership, foreign keys/references, cascade behavior, and orphan policy.
- Check nullability, uniqueness, checks/enums, defaults, timestamps/version fields, and server-generated identifiers against invariants.
- Map representative read/write queries to indexes; flag indexes without a query and high-impact queries without support.
- Check tenant/authorization scoping fields are representable and queryable where needed.
- Review migration/rollout implications separately from steady-state schema quality.
- Exercise constraints with valid and invalid fixture records.
Relevant tools
Schema/migration tools, isolated database, query plans when available.
Safety restrictions
Never run destructive schema experiments against production or irreplaceable data.
Validation
- Important invariants are enforced either by storage constraints or explicitly justified application logic.
- Representative queries match index/relationship design.
- Schema tests/migrations run in an isolated database when available.
Expected output
- Entity/relationship findings
- Missing/excess constraints
- Index rationale
- Executed schema tests
Failure handling
If real access patterns or invariants are unknown, ask from existing product/spec evidence and mark unresolved design choices rather than guessing.
Completion criteria
The skill is complete only when every applicable validation item above has observed evidence or is explicitly marked not executed with the concrete blocker. Do not replace missing evidence with confidence language.
Research mapping
This skill was selected from research problems: P031. See research/vibe-coding-problems.md and research/problem-evidence.csv in the Vibe Coding Skills repository.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.