agentic_coding_lab: Skill for Claude Code

/publish-site — build and publish the results site

The lab has two publishing paths and they are not alternatives:

Path	Produces	Entry point
this skill	the live site on the gh-pages branch, one page per RQ	pnpm deploy:site
/build-overview	a frozen Markdown snapshot under research/reports/	generate-snapshot-skeleton.py

Do not reach for one when the user asked for the other. "Snapshot", "report", "Bericht", "Stand" → /build-overview. "Site", "online", "deploy", "Pages" → here.

What publishes, and what does not

export-site-data.py globs research/questions-*/*/README.md. So the site carries the per-harness and cross-harness RQs only — research/workflow-dev/ and research/kata-dev/ are deliberately not published yet. If the user expects a workflow-development RQ on the site, say that it is out of scope rather than hunting for a bug.

Each RQ page shows its findings.md as written, behind a warning banner. There is no separate review step, so a findings file that contradicts its own data goes online as it stands. Worth a sentence to the user when you know of one.

Deploy is outward-facing

deploy-site.py pushes to a public branch. Never run it without the user saying so in this conversation. Building is free and reversible; deploying is not. When the user asks "how do I publish", answer with the commands and stop — do not deploy to demonstrate.

Phase 1 — preconditions

deploy-site.py refuses on any of these, and it refuses after running its own build, so checking first saves the build. Report them as a block:

cd /path/to/agentic_coding_lab
git rev-parse --abbrev-ref HEAD                      # must be main
git merge-base --is-ancestor HEAD origin/main && echo pushed || echo NOT-pushed
git status --porcelain -- research site | wc -l      # must be 0
command -v uv || echo "uv MISSING"
test -d site/node_modules || echo "site deps MISSING"

Two of these are the traps:

• site/node_modules is not in the repo. Without it the Astro build dies with astro: not found and build-site.py exits 1 after already re-aggregating every RQ. Fix: cd site && pnpm install --frozen-lockfile. Do not worry about the host's pnpm version — corepack honours the packageManager pin in site/package.json and uses that one.
• uv is the documented interpreter and may be absent. Both pnpm scripts are uv run --project ../experiments python .... Install it the way the Dockerfile does, at the same pin, rather than reaching for pip (the system Python is PEP 668 managed and has no ensurepip):

  curl -LsSf https://astral.sh/uv/0.12.17/install.sh | sh
  cd experiments && uv sync