audit-schema

Compare PocketBase rule strings against specs and report coverage gaps.

Updated Aug 23, 2026

Search Tags:#automation #testing #validation #schema #audit #coverage #pocketbase

Ready to run

npx skills add https://github.com/jluckyiv/rivcomocktrial --skill audit-schema

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-schema
Source: https://github.com/jluckyiv/rivcomocktrial/tree/main/.claude/skills/audit-schema
Command: npx skills add https://github.com/jluckyiv/rivcomocktrial --skill audit-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify drift between live PocketBase rule strings and their spec coverage to surface inconsistencies in lockdown.

Core Features & Use Cases

Enumerates collections from pocketbase-types.ts
Fetches live rules from the test PocketBase instance
Compares each collection's 5 rule slots against corresponding specs and reports coverage gaps
Generates a structured findings report with a severity-ranked matrix

Quick Start

Run the audit-schema skill to generate a live coverage report.

Frequently Asked Questions about audit-schema

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

FAQPage Schema

How do I audit PocketBase collection rules for security coverage gaps?▼

To audit PocketBase collection rules, compare live rule strings fetched from your test instance against corresponding spec definitions in web/src/lib/schema. This process enumerates collections from pocketbase-types.ts and checks all five rule slots (list, view, create, update, delete) to surface inconsistencies.

What is PocketBase rule drift and how do I detect it?▼

PocketBase rule drift occurs when live rule strings in your database diverge from their intended spec coverage, creating lockdown inconsistencies. You detect this drift by applying an audit schema that compares each collection's five rule slots against corresponding specifications to produce a structured findings report with severity rankings.

Can I validate PocketBase schema lockdowns across all collections automatically?▼

You can validate PocketBase schema lockdowns automatically by enumerating all collections defined in pocketbase-types.ts. The audit fetches live rules from the test PocketBase instance and compares every rule slot against corresponding specs to generate a coverage matrix with severity-ranked findings guiding remediation.

How do I generate a coverage matrix for PocketBase collection rules?▼

Generating a coverage matrix for PocketBase collection rules requires fetching live rules from your test instance and comparing them against specs in web/src/lib/schema. The output is a structured findings report with a severity-ranked matrix that guides remediation of lockdown inconsistencies.

What specs do I need to run a PocketBase schema audit?▼

Running a PocketBase schema audit requires spec files located in web/src/lib/schema and collection type definitions in pocketbase-types.ts. You also need access to a live test PocketBase instance to fetch current rule strings for comparison against those corresponding specifications across all five rule slots.

Why are my PocketBase collection rules inconsistent with my schema specs?▼

PocketBase collection rules become inconsistent with schema specs due to drift between live rule strings and their spec coverage. An audit-schema process identifies this drift by enumerating collections from pocketbase-types.ts, fetching live rules, and comparing each rule slot against corresponding specs to produce severity-ranked findings.