system-reality-auditor

Synchronizes codebase, database schema, and documentation via a triple-point audit.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/theeabrarrr/LPG-Connect --skill system-reality-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-reality-auditor
Source: https://github.com/theeabrarrr/LPG-Connect/tree/main/.agents/skills/system-reality-auditor
Command: npx skills add https://github.com/theeabrarrr/LPG-Connect --skill system-reality-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align master project documents with the actual system state by performing a triple-point audit across codebase, database schema, and documentation.

Core Features & Use Cases

  • Code Audit: map implemented features, verify the presence of UI components, server actions, helpers, and API routes.
  • DB Audit: fetch the latest database schema, inspect tables, columns, and RPCs.
  • Alignment & Update: reconcile Code and DB findings with master project documents, and rewrite Status and Gaps to reflect ground truth.

Quick Start

Run a triple-point audit to reconcile code, database schema, and documents with current system reality.

Frequently Asked Questions about system-reality-auditor

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

FAQPage Schema
How do I align my project documentation with the actual codebase and database state?

Performing a triple-point audit synchronizes your codebase, database schema, and documentation by comparing implemented features and DB structure against master documents, then rewriting Status and Gaps sections to reflect ground truth.

What is a triple-point audit for codebase and database alignment?

A triple-point audit synchronizes codebase, database schema, and documentation by mapping implemented features, inspecting DB tables and RPCs, and updating master documents to match the live system.

How do I update PRD and GAP_ANALYSIS documents based on current system reality?

To update PRD and GAP_ANALYSIS documents, run an audit that verifies implemented UI components and API routes, inspects database tables and RPCs, and rewrites Status and Gaps sections to match verified code and DB findings.

Can I audit database schema and codebase features without external dependencies?

Yes, you can audit database schema and codebase features without external dependencies by mapping implemented UI components, server actions, and API routes while fetching DB tables and RPCs to reconcile against documentation.

What is the best way to find gaps between master project documents and live code?

The best way to find gaps between master documents and live code is running a triple-point audit that maps implemented features, fetches database schema, and rewrites the Gaps section based on coordinated code and DB findings.

When should I run a code and DB alignment audit for my project?

Run a code and DB alignment audit when master documents like PRD, GAP_ANALYSIS, and EXECUTION_PLAN need to reflect current system reality, ensuring documentation matches implemented features, database tables, and RPCs.