sqlite

Name: sqlite
Availability: InStock
Author: evgeniifenita

Guide SQLite schema changes and migrations for Librova's native persistence layer.

Updated Aug 27, 2026

Search Tags:#debugging #sqlite #sql #persistence #c++#schema-migration #fts

Ready to run

npx skills add https://github.com/EvgeniiFenita/Librova --skill sqlite-evgeniifenita

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sqlite
Source: https://github.com/EvgeniiFenita/Librova/tree/main/.agents/skills/sqlite
Command: npx skills add https://github.com/EvgeniiFenita/Librova --skill sqlite-evgeniifenita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Librova's native persistence layer relies on SQLite for structured storage. This skill provides focused guidance to keep schema changes, queries, and FTS behavior aligned with Librova's architecture and failure model, preventing regression and unsafe patterns.

Core Features & Use Cases

Schema inspection and alignment with Librova's codebase and migration policy.
Review and guidance for SQL changes in libs/Database, including migrations and FTS queries.
Best practices for using Librova wrappers, path encoding, and deterministic query patterns.

Quick Start

Review the current Librova SQLite guidance and apply it before making changes to the native persistence layer.

Frequently Asked Questions about sqlite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I safely update the SQLite schema in a native C++ persistence layer?▼

To safely update the SQLite schema in a native C++ persistence layer, you must adhere to the project's specific migration rules and use its designated SQL wrappers to prevent regressions and maintain consistency.

What is the best way to manage SQLite schema migrations without breaking existing queries?▼

Managing SQLite schema migrations safely requires aligning changes with the current codebase architecture and applying explicit maintenance patterns to ensure existing queries and wrappers continue functioning without regressions.

How do I maintain SQLite FTS indexing queries when modifying database schemas?▼

Maintaining SQLite FTS indexing queries during schema modifications requires following explicit FTS maintenance patterns to ensure search behavior remains aligned with the native persistence layer's failure model.

Does this SQLite guidance apply to general database debugging or a specific C++ codebase?▼

This SQLite guidance applies specifically to a native C++ persistence layer rather than general database debugging, focusing on schema alignment, migrations, and deterministic query patterns within that targeted codebase.

Why do I need specific SQL wrappers for SQLite schema changes instead of writing raw queries?▼

Specific SQL wrappers are needed for SQLite schema changes to enforce deterministic query patterns and path encoding, preventing unsafe modifications that could cause regressions in the native persistence layer.