publishing-trigger-check

Topics in the source

• Publishing trigger check
• Use when
• Callable command
• Companion-site release audit

Run after changing .github/workflows/deploy-pages.yml (the real path GitHub Actions executes) or family/skill folder conventions. It reuses the repository's existing verify-deploy-trigger.mjs. The check requires the workflow to contain a family-independent /FAMILY.md or /SKILL.md glob, rejects hardcoded current family names, and exits non-zero when the workflow is absent or unsafe. It never pushes, publishes, force-pushes, or handles tokens. From a network-enabled environment, run: This independently probes OverKill Hill, Glee-fully Tools, and AskJamie for home/about/legal/sitemap responses, canonical and OG metadata, OG image reachability, sitemap samples, CNAME alignment, workflow deploy handoff, and repository-vs-live freshness. Add --json for archival automation output. --strict blocks when a repository has no proven deploy step; this currently identifies a site as blocked only when neither a repository deploy step nor a successful GitHub-managed Pages run can be proven. If GitHub manages the deployment outside repository YAML, the runner reports that limitation explicitly rather than silently treating validation as publishing. It does not infer or change DNS, repository settin

This is an excerpt. Refer to the complete source and its current requirements.