Verified:GitHub

version-tracker-db-init

Q: How to create the version tracker tracking database?

Create the target directory, then run sqlite3 against the database path with the canonical schema.sql as input. Confirm success by checking that error_classification contains exactly 12 seed rows.

Q: Does SQLite support concurrent readers and writers?

SQLite WAL mode allows concurrent readers during writes, which this schema enables. However, concurrent writers should still be avoided to prevent lock contention.

Q: Why are foreign keys not enforced in my SQLite database?

SQLite requires PRAGMA foreign_keys = ON on every connection; it is off by default. The schema sets it during initialization, but ad-hoc sqlite3 CLI sessions must enable it manually.

Q: How are timestamps and JSON stored in SQLite?

Timestamps are stored as ISO 8601 text, which sorts correctly lexicographically. JSON is stored as TEXT and queried with json_extract(col, '$.key').

Initializes the version-tracker SQLite database with schema, indexes, and seed data.

1|Updated Aug 11, 2026

Search Tags:#schema #sqlite #seed data #version tracking #ddl #bug bounty #database initialization

One-click install

npx skills add https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework --skill version-tracker-db-init-maybe4a6f7365

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: version-tracker-db-init
Source: https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework/tree/main/version-tracker/skills/version-tracker-db-init
Command: npx skills add https://github.com/Maybe4a6f7365/agentic-bug-bounty-framework --skill version-tracker-db-init-maybe4a6f7365

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up the version-tracking database manually is error-prone: missing tables, forgotten indexes, or absent seed rows break downstream tracking workflows. This Skill creates the complete SQLite database from the canonical schema in one verified pass. ## Core Features & Use Cases - Schema Creation: Applies the canonical DDL to create 16 tables covering platforms, programs, targets, assets, scope observations, version events, findings, and research notes. - Seed Data Loading: Inserts 12 error classification rows with auto-actions so error handling works from the first run. - Built-in Verification: Provides SQL checks confirming row counts, WAL journal mode, and foreign key enforcement. - Use Case: When deploying the version tracker on a new machine or recovering from a corrupted database file, run this Skill to recreate the database and confirm it matches the expected schema before resuming tracking. ## Quick Start Initialize the version tracker database by applying the canonical schema to a new SQLite file and verify the error classification seed rows.

Frequently Asked Questions about version-tracker-db-init

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

FAQPage Schema

How do I initialize a SQLite database from a schema file?▼

Run sqlite3 with the database path and pipe the schema file into it: sqlite3 "$DB_PATH" < schema.sql. Verify creation with sqlite3 "$DB_PATH" ".tables" to list all created tables.

How to create the version tracker tracking database?▼

Create the target directory, then run sqlite3 against the database path with the canonical schema.sql as input. Confirm success by checking that error_classification contains exactly 12 seed rows.

Does SQLite support concurrent readers and writers?▼

SQLite WAL mode allows concurrent readers during writes, which this schema enables. However, concurrent writers should still be avoided to prevent lock contention.

Why are foreign keys not enforced in my SQLite database?▼

SQLite requires PRAGMA foreign_keys = ON on every connection; it is off by default. The schema sets it during initialization, but ad-hoc sqlite3 CLI sessions must enable it manually.

How are timestamps and JSON stored in SQLite?▼

Timestamps are stored as ISO 8601 text, which sorts correctly lexicographically. JSON is stored as TEXT and queried with json_extract(col, '$.key').