Menú
Validate release readiness - changesets, policy compliance, build, test, and dependency sync
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | release-check |
| description | Validate release readiness - changesets, policy compliance, build, test, and dependency sync |
| disable-model-invocation | true |
Run a comprehensive validation before merging to main or publishing.
Run each step and report results. Stop early if a critical failure is found.
Check branch state
git status
git log --oneline main..HEAD
Verify: clean working tree, commits ahead of main
Verify changesets exist for affected packages
ls .changeset/*.md 2>/dev/null
pnpm nx affected --base=main -t build --dry-run
Cross-reference: every affected non-private package should have a changeset entry. Packages in the changeset ignore list (dill-docs, repopo-docs) can be skipped. Verify bump types make sense (patch for fixes, minor for features, major for breaking).
Policy compliance
./packages/repopo/bin/dev.js check
Must pass with zero violations.
Dependency sync
pnpm syncpack list-mismatches
Must have zero mismatches.
Build all affected packages
pnpm nx affected -t build --base=main
Must succeed with no errors.
Run all affected tests
pnpm nx affected -t test --base=main
Must pass with no failures.
Format and lint check
pnpm nx affected -t check --base=main
pnpm nx affected -t lint --base=main
Must pass with no issues.
Summarize results:
Add a new OCLIF command to a CLI package with proper base class, flags, args, and post-creation steps
Create changesets for pending changes by analyzing git diff and commit history
Audit workspace dependencies for version mismatches, unused packages, and sync issues across all packages
Fix all repository policy violations
Run Nx affected commands for the current changes
Reference for Nx task architecture, orchestration patterns, and how to add or modify build tasks