verificar-app

Validates JSX transpilation and data invariants before committing the Armado en México app.

Updated Jun 10, 2026
One-click install
npx skills add https://github.com/saulo-fl/armado-en-mexico --skill verificar-app-saulo-fl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verificar-app
Source: https://github.com/saulo-fl/armado-en-mexico/tree/main/.claude/skills/verificar-app
Command: npx skills add https://github.com/saulo-fl/armado-en-mexico --skill verificar-app-saulo-fl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @babel/standalone.

What problem does it solve? A syntax error in a .jsx file or inconsistent data in the data-*.js files can silently break the app in production, since no automated test suite catches these issues. This Skill runs a mandatory pre-commit verification that transpiles all JSX with Babel, loads the data files in Node, and audits data invariants before anything is published. ## Core Features & Use Cases - Full build verification: Runs npm run build to transpile .jsx to .js and prerender all HTML pages, failing fast if the build breaks. - Data integrity audit: Executes auditar.js to check that priceExact matches the last history record, ids are contiguous, stock is positive, histories are chronological, and branch counts are correct. - Single-file transpilation: Provides a one-liner to transpile an individual .jsx file with @babel/standalone while iterating on a screen. - Use Case: After editing a weapon's price history or a screen component, run this Skill to confirm the build passes and the audit ends with "AUDITORÍA SIN HALLAZGOS" before committing. ## Quick Start Verify the app by running the build and the audit script, then confirm the audit reports no findings before I commit my data and screen changes.

Frequently Asked Questions about verificar-app

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

FAQPage Schema
How do I verify a JSX app before committing changes?▼

Run npm run build to transpile all .jsx files to .js and prerender the HTML pages, then run the auditar.js script with Node. Do not commit if either step fails, since the deploy would publish HTML pointing to missing JavaScript files.

How to transpile a single JSX file with Babel standalone?▼

Load @babel/standalone in Node, read the .jsx file with fs, and call Babel.transform with the react preset and the correct filename. This prints OK if the file transpiles, letting you iterate on one screen without a full build.

Why does piping the audit script to tail hide failures?▼

Piping node auditar.js to tail makes $? return the exit code of tail, which is always 0, so the audit appears to pass even when it fails. Run node auditar.js directly or use set -o pipefail to preserve the real exit code.

What data invariants should a price history audit check?▼

The audit checks that priceExact equals the last history record for every item, ids are contiguous, stock is greater than zero, histories are chronological, and the source inventory matches the last history record across weapons, accessories, and ammunition.

Can I test the app in a real browser instead of Node?▼

No, because there is no network access to load unpkg dependencies in a browser. Transpilation with Babel standalone plus loading the data files in Node with a window shim is the designated substitute for browser testing.