full-stack-audit

Compares Dart frontend and Python backend files to detect cross-stack field and schema mismatches.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/yunior123/origna_gta_firebase --skill full-stack-audit-yunior123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-stack-audit
Source: https://github.com/yunior123/origna_gta_firebase/tree/main/.claude/skills/full-stack-audit
Command: npx skills add https://github.com/yunior123/origna_gta_firebase --skill full-stack-audit-yunior123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend and backend codebases drift apart over time, causing runtime failures from mismatched field names, enums, and payload structures between the Flutter app and Firebase Functions. This Skill systematically audits every cross-stack interface to surface inconsistencies before they reach production. ## Core Features & Use Cases - Paired File Comparison: Reads 11 defined frontend-backend file pairs (checkout, orders, products, auth, shipping, subscriptions, returns, notifications) and compares field names, types, enums, error handling, and response formats. - Schema Constant Verification: Checks that schema_constants.dart and schema_constants.py remain identical, plus field-by-field comparison of generated Dart models against Python models. - Standardized Mismatch Reporting: Reports every inconsistency in a standard MISMATCH format for easy triage. - Use Case: After adding a new order field in the Python handler, run the audit to confirm the Dart order models and checkout provider send and parse the same field name and type. ## Quick Start Ask the assistant to run a full-stack audit of the Flutter app against the Firebase Functions backend and report all field and enum mismatches.

Frequently Asked Questions about full-stack-audit

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

FAQPage Schema
How do I check frontend and backend field name consistency?▼

Run the full-stack audit, which reads paired Dart and Python files and compares field names, types, and enums across each interface. It reports every mismatch in a standard format covering checkout, orders, products, auth, and more.

How to detect schema drift between Flutter and Firebase Functions?▼

The audit compares schema_constants.dart against schema_constants.py, which must be identical, and checks generated Dart models field-by-field against Python models. Any drift in constants or model definitions is flagged.

What file pairs does the cross-stack audit compare?▼

It covers 11 pairs: checkout, seller and buyer orders, product CRUD, auth/admin, schema constants, order/product/user models, shipping, digital products, subscriptions, returns, and notifications.

Does the audit fix mismatches automatically?▼

No, it only detects and reports mismatches in a standard MISMATCH format. Developers review the report and apply corrections to the Dart or Python side manually.

When should I run a full-stack consistency audit?▼

Run it after changing any API payload, adding model fields, or modifying enum values on either stack. It is most useful before releases to catch contract drift between the app and backend handlers.