← ClaudeAtlas

getscribe-site-synclisted

Audit and re-deploy the getscribe.dev marketing site whenever scribe ships a new release. Use this whenever a new scribe version is tagged or pushed, a new CHANGELOG entry lands, or the user says anything like "sync the site", "update getscribe.dev", "the site is stale", "check the site against the changelog", "did the landing page get updated for this release", or after running `git tag v*`. Also use it proactively when you notice the latest git tag / top CHANGELOG entry is newer than what the site copy reflects. The site is deliberately VERSION-FREE — this skill keeps it factually current with the CHANGELOG while enforcing that no version string ever leaks onto any surface, then deploys to Cloudflare and verifies the live result.
oliver-kriska/scribe · ★ 8 · DevOps & Infrastructure · score 71
Install: claude install-skill oliver-kriska/scribe
# getscribe.dev release sync ## Why this skill exists `site/` is the source for <https://getscribe.dev>, deployed via Cloudflare Workers static assets. It is **not** hand-edited on every patch release, so any `v0.2.x` string baked into it rots the moment the next release ships — and a stale version is the first thing a visitor (or a shared social card) sees. The hard-won rule from past cleanups: **the site states current capability in the present tense and carries no version number anywhere.** When a release changes what is true, you update the *claim*, never add an "as of vX" note. This skill is **invoked manually** — by the maintainer asking for it, or by Claude noticing the page is stale. It is not wired to anything that runs on its own. There is an optional, *warn-only* git hook that prints a reminder when a release tag is created (see `references/release-automation.md`); it never deploys and never runs an LLM — refreshing the site is always a deliberate act. Once invoked, run the full loop end-to-end without pausing: figure out the release delta from the CHANGELOG, audit every surface for version pins and now-false claims, fix the copy in the evergreen voice, regenerate the social card if its text changed, deploy, verify the live site, commit, then report. The maintainer triggered it on purpose — don't stop midway to ask permission. ## The cardinal invariant **No version string on any surface, ever.** That means: no `v0.2.x`, no bare `0.2.x`, no `softwareVersion` i