spacevibe-deck: Skill for Claude Code

landing-sync — does the landing still describe the app?

The landing is hand-copied from the app. A few files import app code; everything else restates the app in prose, fixtures and comments that cite the app source they mirror. .github/workflows/landing.yml runs only on marketing/**, so a change under src/, electron/ or docs/ never fails a landing check. This skill is that check, run by hand.

Read-only by default. Produce the report, stop, and wait for the owner. Do not edit anything under marketing/ in the same pass — see "After the report". The disallowed-tools frontmatter blocks the edit tools while this skill runs, but Bash can still write, so the read-only rule still binds.

Shell state does not survive between tool calls, so step 0 writes the three values every later block needs to /tmp/landing-sync.env, and every block opens by sourcing it. Never retype a hash from memory; re-source the file.

0. Pick the revision

Arguments: $ARGUMENTS. Empty → judge origin/main from the last commit that touched the landing. <base> → that base, still judging origin/main. <base>..<rev> → both given. The production landing deploys from origin/main; the primary checkout can be far ahead of it and dirty, so the judged revision is checked out into a scratch worktree and nothing below reads the checkout you were started in.

REV=origin/main                                   # or the <rev> half of the argument
git fetch origin --quiet
W=/tmp/landing-sync-$(git rev-parse --short "$REV")
[ -d "$W" ] || git worktree add --detach --quiet "$W" "$REV"
cd "$W"
BASE=$(git log -1 --format=%H -- marketing/landing-prototype marketing/stage)   # or the <base> argument
printf 'REV=%s\nW=%s\nBASE=%s\n' "$(git rev-parse HEAD)" "$W" "$BASE" > /tmp/landing-sync.env
cat /tmp/landing-sync.env; git log -1 --format='%h %ad %s' --date=short "$BASE"

A landing commit resets the baseline only for what it touched. Drift older than the base is caught by the state passes in step 3 (c, d, e), which do not depend on the range, so run them every time.