publicar

Automates git commits, pull requests, and Cloudflare Pages deployment for armado.mx.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about publicar

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

FAQPage Schema
How do I deploy a static site to Cloudflare Pages from git?▼

Cloudflare Pages rebuilds automatically when you merge into the connected branch, here main, using the build command npm ci && npm run build with output directory out. Merging the pull request triggers the deploy, which takes about one to two minutes.

How do I force browsers to reload cached JavaScript data files?▼

Append a version query suffix like ?v=20260617 to the script src URLs and bump it whenever the data changes. The browser treats the new URL as a distinct resource and downloads a fresh copy instead of using the cached file.

Why does my git push revert changes already on main?▼

This happens when your branch is based on a stale local main because merges happened on GitHub. Always run git fetch origin main and create branches from origin/main, or rebase onto it with git rebase --onto before pushing.

How do I verify a Cloudflare D1 binding is still active after deploy?▼

Send a POST with an invalid JSON body to an append endpoint; a json_invalido response confirms the D1 binding works, while sin_backend means the binding was lost. A 200 on a state endpoint is not a valid probe since it responds identically with or without the binding.

Why is Cloudflare serving old JavaScript after a successful deploy?▼

The zone-level Browser Cache TTL setting can override origin cache headers and keep serving stale files for hours. Compare cache-control headers between the pages.dev origin and the production domain; if they differ, fix the setting in the Cloudflare dashboard, not the repo.