pinta

Cut a new Pinta release end-to-end. Bumps versions, updates CHANGELOG, builds + zips the extension, commits, tags, pushes, publishes pinta-companion to npm, and creates a GitHub release with the zip attached. Chrome Web Store upload is the only manual step left (Google doesn't expose a key-free publish API).

Use when the user wants to visually annotate their running app to make UI changes. Picks up annotation sessions submitted from the Pinta Chrome extension and edits the matching component files in the user's project. Accepts an optional `--push` (default) or `--polling` argument controlling how the agent waits for sessions.

Use when the user wants to visually annotate their running app to make UI changes. Picks up annotation sessions submitted from the Pinta Chrome extension and edits the matching component files in the user's project. Accepts an optional `--push` (default) or `--polling` argument controlling how the agent waits for sessions.

Use when the user wants a security + performance audit of the Pinta Chrome extension. Walks the manifest, content scripts, service worker, message passing, WebSocket / HTTP layer, IndexedDB store, composite + screenshot pipeline, and Svelte 5 runes usage; produces a prioritized findings list with file:line refs and concrete fixes.

Use when the user wants a single-shot release-readiness check before shipping Pinta. Runs `/test`, `/audit`, and `/spec` in sequence and produces one consolidated verdict — green-light to publish, fix-the-criticals-and-ship, or hold. Recommended before any `npm publish`, `git tag`, or Chrome Web Store push.

Use when the user wants to find gaps between Pinta's design spec and the actual codebase before a release. Walks every section of `spec/SPEC.md`, verifies each requirement against the current `extension/`, `companion/`, and `skill/` source, and produces a prioritized punch list of: (a) spec items not implemented, (b) spec sections out of date with shipped code, (c) phases marked Shipped that aren't actually complete, (d) wire-protocol drift between extension and companion, (e) docs (README/CHANGELOG) out of sync. Recommended before cutting any version tag.

Use when the user wants to run the Pinta test suite (Vitest) — runs unit tests for the Chrome extension and companion server. Accepts an optional workspace name (`extension` or `companion`) to scope the run; defaults to running both.

Use when the user wants to build and install Pinta from scratch — installs npm dependencies, builds the Chrome extension and the companion server, installs the Claude Code skill into ~/.claude/skills/pinta/, and prints the steps to load the unpacked extension in Chrome. One-shot setup.