cocode: Skill for Claude Code

Releasing cocode

The procedure is the workspace release play, docs/workspace/releasing.md at the workspace root — read it first, then run it with what follows. The repo key is cocode, the base is dev, and the pull request targets main: guard-branches.yml's gate-main job refuses any head branch into main that does not match ^release\/v[0-9]+\.[0-9]+\.[0-9]+$, so there is no other way in. The release worktree is _cocode--release, made with wt add cocode release --branch release/vX.Y.Z. The repo declares neither .worktree.toml nor .worktreeinclude, so wt resolves the base from origin/dev, copies .env when the main checkout has one, and provisions with the Makefile's install target (uv sync --all-extras --no-cache), which is what creates the .venv every gate below runs out of — and --all-extras is why mkdocs is there for the docs gate.

What ships

The merge to main is a push to main, and both publishing workflows fire on it:

• The cocode package on PyPI, by publish-pypi.yml — python3 -m build, then trusted publishing into the pypi environment at https://pypi.org/p/cocode. The upload sets no skip-existing, so a push to main that did not bump the version fails there: version-check.yml runs on pull requests only, and nothing else stands between an unbumped push and the upload.
• The GitHub Release and the vX.Y.Z tag, by the same workflow's github-release job. It reads the number with grep -m 1 'version = ' pyproject.toml, slices the notes out of CHANGELOG.md between the ## [vX.Y.Z] - heading and the next ## [v…] - one, signs the dists with Sigstore, creates the Release with gh release create, and uploads the signature bundles. The signing step comes before the Release is created and is not continue-on-error, so a Sigstore failure leaves the version on PyPI with no Release and no tag; the recovery is re-running that run's failed jobs, which replays github-release alone, since the upload already succeeded and a full re-run would meet the dists already on PyPI. When the changelog slice comes up empty the step warns, sets the notes empty and exits 0, so the Release ships carrying the bare line Release vX.Y.Z instead of failing.
• The documentation site, by deploy-docs.yml — make install, then uv pip install -e ".[docs]", then make docs-deploy (mkdocs gh-deploy --force --clean) onto gh-pages, served at https://pipelex.github.io/cocode/. gh-deploy is not strict, so a broken build publishes rather than failing, which is what the docs gate below is for.