Is it safe to delete tables using this workflow?

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.

How does this skill identify unused tables?

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.

Does it perform automatic migrations?

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

Why should I audit my persistence layer regularly?

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.

Can this handle databases other than SQLite?

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

Name: Persistence Layer Auditor
Author: smith6jt-cop

bysmith6jt-cop

데이터베이스 관리

Audits and optimizes SQLite persistence layers by identifying unused tables, broken method calls, and schema inconsistencies.

소개

The Persistence Layer Auditor provides a systematic framework for maintaining database health and ensuring alignment between your SQL schema and application code. It automates the process of identifying schema drift, detecting unreferenced database methods, and pruning bloated tables that are no longer in use. By combining recursive grep-based analysis with direct SQLite querying, this skill helps developers resolve foreign key conflicts and maintain a lean, efficient interface between their database manager and execution logic, which is especially critical for data-intensive applications like trading systems.

주요 기능

0 GitHub stars
Automated detection of unreferenced database methods via grep
Comprehensive SQLite table usage and row-count analysis
Validation of foreign key constraints during table removal
Schema optimization and pruning for obsolete data structures
Idempotent migration patterns using CREATE TABLE IF NOT EXISTS

사용 사례

Refactoring legacy database schemas to remove obsolete tracking tables
Identifying 'dead' database manager methods that no longer have active callers
Ensuring database schema consistency across environments after major code updates

소개

주요 기능

0 GitHub stars
Automated detection of unreferenced database methods via grep
Comprehensive SQLite table usage and row-count analysis
Validation of foreign key constraints during table removal
Schema optimization and pruning for obsolete data structures
Idempotent migration patterns using CREATE TABLE IF NOT EXISTS

사용 사례

Refactoring legacy database schemas to remove obsolete tracking tables
Identifying 'dead' database manager methods that no longer have active callers
Ensuring database schema consistency across environments after major code updates