メニュー
Prepare Codex harness package releases with version checks, package dry-runs, npm publish readiness, release notes, verification evidence, and rollback notes. Use before publishing or tagging releases.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Define UI design specs, route contracts, visual states, accessibility expectations, and UI/API synchronization before frontend implementation. Use for new screens, redesigns, visual QA, or UI contract updates.
Automatically synchronize documentation with code changes across all project phases. Detects file changes, categorizes update types, auto-generates API docs, changelog entries, implementation handoffs, and validates cross-reference integrity. Use after any phase implementation.
Initialize and operate a project planning harness for Codex. Use this skill when the user types /init, asks to create a new project, add a feature, fix a bug, plan work, generate tests first, update docs, track phases, review changes, audit a repository, or manage architecture decisions.
Create premium frontend web designs and usable first-screen experiences for new websites, web apps, dashboards, tools, and landing pages. Use when Codex is asked to design or build a new frontend UI, create a fresh page or app experience, choose a visual direction for a new product surface, or turn a product brief into implementation-ready React, Next.js, Tailwind, CSS, or HTML.
Create decision-complete plans for Codex harness work, including tests, fixtures, contracts, memory updates, verification, and recovery. Use for new features, refactors, bug fixes, audits, or multi-phase autonomous work.
Auto-enforce research-first pattern - automatically research documentation, best practices, and GitHub before any important decision. Research output feeds directly into planning. Triggered automatically for features, bugs, architecture changes, and spec updates.
| name | genesis-release |
| description | Prepare Codex harness package releases with version checks, package dry-runs, npm publish readiness, release notes, verification evidence, and rollback notes. Use before publishing or tagging releases. |
Ensure package releases are verified, reproducible, and reversible.
Use before npm publish, version bumps, release notes, or release automation changes.
Do not use for local-only edits that will not be packaged or released.
Target version, changed files, verification output, package contents, and publish credentials status.
Release checklist, package dry-run evidence, release notes, known risks, and rollback instructions.
Run verify, eval, package dry-run, and CLI smoke tests.
Update release fixtures or package content expectations when packaging changes.
Update public contract docs when release changes CLI or skill behavior.
Update current state and known problems after release preparation.
Read package metadata and release memory first; do not re-scan unchanged skill bodies.
Tarball contents are correct and release notes explain behavior, tests, and risks.
Publishing cache files, missing executable scripts, and omitting npm 2FA/token readiness.
If publish fails, capture error, update known problems, do not change version until root cause is fixed.
This skill incorporates the Release & Deployment Orchestration Standard to manage production-ready releases and rollbacks using the provided templates and playbooks:
checklists/pre-release-validation.md, checklists/post-deployment-verification.md)
playbooks/semantic-versioning-automation.md, playbooks/canary-deployment-orchestration.md)
observability/release-tracking.md)
templates/deployment-strategy-template.md, templates/release-runbook-template.md)
checklists/checklist.md, checklists/pre-release-validation.md, checklists/post-deployment-verification.mdplaybooks/semantic-versioning-automation.md, playbooks/canary-deployment-orchestration.mdobservability/release-tracking.mdtemplates/release-checklist-template.md, templates/deployment-strategy-template.md, templates/release-runbook-template.md