Review database design for good practices beyond SQL syntax. Use when auditing referential integrity, foreign key constraints, orphaned records, plain-text storage of sensitive data (tokens, credentials, API keys), Liquibase migration completeness, or missing table/column documentation.
Apply this skill to the full database schema as represented in migration files, focusing on design quality independent of SQL syntax.
backend/src/main/resources/db/backend/src/main/resources/liquibase.yml| Severity | file/path | description of issue | concrete suggestion || Severity | Meaning |
|---|---|
| High | Plain-text credential storage, missing FK constraint, or broken migration chain |
| Medium | Missing index, orphaned data risk, or unclear column purpose |
| Low | Missing column comment or minor documentation gap |
access_token, token, secret, api_key, password stored as plain TEXT without encryption noteFOREIGN KEY constraint defined in migrationschangeSet that alters or drops data without a corresponding rollbackuser_id (orphan risk if user is deleted)liquibase:rollback tags on destructive changes