Menu
Cut a production release: tag, wait for CI, write release notes, publish latest.json.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Run pre-push checks including typecheck and tests.
Generate concise user-facing release notes between two versions.
Interactively investigate a bug by grilling the user, exploring the codebase for suspects and solutions, suggesting related test scenarios, and then creating a well-structured GitHub issue via `gh` CLI. Use when the user wants to report a bug, file an issue, create a GitHub issue, or says things like "file a bug", "create an issue", "report this bug", "open an issue", or "github issue". Also trigger when the user describes unexpected behavior and wants to track it formally.
Import PDF documents into Seed Hypermedia using AI-powered content recognition. Use when the user wants to convert a PDF file into a Seed document, extract content from PDFs for Seed, or ingest PDF files into the Seed platform. This is an LLM-powered alternative to the CLI's built-in `document import` command -- the LLM reads the PDF visually and produces structured Seed content with superior OCR, layout recognition, and semantic understanding.
| name | run-release |
| description | Cut a production release: tag, wait for CI, write release notes, publish latest.json. |
Execute the release process in docs/releasing.md. That doc is canonical for the process details;
this skill is the interactive runbook. Invoking this skill counts as explicit permission to create
and push the release tag, but confirm the version number with the user before pushing it.
main, the working tree is clean, and local main matches
origin/main. Abort and report if not.YYYY.M.N, see docs/releasing.md): check
git tag --sort=-creatordate | head -5. If the latest tag is from the current month, increment
its last number; otherwise start at .1 for the current month.git tag <version> && git push origin <version>.Release - Desktop App, Release - Docker Images) to go
green: gh run list --workflow release-desktop.yml, then gh run watch <run-id>. Builds take
tens of minutes — keep waiting, don't proceed early. If a workflow fails, stop and report.<prev-tag>..<version> following the voice, grouping, and
exclusion rules in the releasenotes skill, but match the exact format of the last few
published releases (gh release view <prev-tag>). Key rules from docs/releasing.md:
**Full Changelog** compare link.gh release edit <version> --notes-file <tmpfile> --prerelease=false --latest
(the workflow creates the release as a prerelease; this promotes it).gh workflow run "Generate latest.json (prod)" and confirm the run succeeds.