Persistence Layer Auditor FAQs

Question 1

Is it safe to delete tables using this workflow?

Accepted Answer

Yes, the skill includes critical safety checks for foreign key constraints and requires a verification step to ensure no callers exist before any deletion occurs.

Question 2

How does this skill identify unused tables?

Accepted Answer

It combines SQLite row counts with recursive grep searches across the codebase to find any logic that references specific table names or associated database manager methods.

Question 3

Does it perform automatic migrations?

Accepted Answer

It provides a verified workflow for manual cleanup and recommends using idempotent SQL commands to handle schema updates safely without breaking existing data.

Question 4

Why should I audit my persistence layer regularly?

Accepted Answer

As code evolves, databases often accumulate 'schema drift'—unused tables and methods that increase complexity and storage overhead. Regular audits keep the data layer performant and maintainable.

Question 5

Can this handle databases other than SQLite?

Accepted Answer

While the specific commands are optimized for SQLite's local file structure, the methodology of cross-referencing schema usage with codebase grep searches applies to most relational databases.

Persistence Layer Auditor

Key Features

Use Cases

Persistence Layer Auditor

Key Features

Use Cases