What problem does it solve? Publishing changes to the armado.mx production site involves a fragile multi-step git and deployment workflow: stale local main branches can silently revert work, data file changes need manual cache-busting, and backend D1 binding failures are silent. This Skill encodes the exact procedure and hard-won gotchas so nothing is missed. ## Core Features & Use Cases - Safe branching and merging: Enforces fetching a fresh origin/main before creating work branches, rebasing when based on stale main, and merging twin PRs to main and develop with --match-head-commit verification. - Cache-busting for data files: Bumps the ?v= suffix on data-*.js script tags in index.html and admin.html whenever data changes, preventing stale browser caches. - Deployment verification: Provides curl probes to confirm the D1 backend binding and Access variables survived a deploy, plus preview-branch validation before merging. - Use Case: After editing the weapons catalog data, run the build and audit, commit, push, open twin PRs to main and develop, verify the preview deploy, then merge to publish on armado.mx. ## Quick Start Commit my changes, open the twin pull requests to main and develop, and walk me through publishing to production following the publicar workflow.