Update to Codex Dev Workflows

{
  "description": "Assess whether a software change is ready to release by checking scope, validation, risk, operations, and rollback readiness.",
  "included_files": [],
  "name": "pre-release-review",
  "skill_md_contents": "---\nname: pre-release-review\ndescription: Assess whether a software change is ready to release by checking scope, validation, risk, operations, and rollback readiness.\n---\n\n# Pre-release review workflow\n\nUse this skill before shipping a release, demo, beta, or major milestone. Read the release scope, acceptance criteria, repository instructions, testing docs, deployment/runbook material, and changelog/release notes when present. This is a review: do not publish, deploy, tag, or modify external systems unless the user explicitly authorizes it.\n\n## Readiness review\n\n1. Confirm the intended release contents and identify deliberate exclusions.\n2. Review the diff for correctness, compatibility, migrations, feature flags, configuration, upgrade/downgrade concerns, and user-visible behavior.\n3. Verify evidence from required tests, static analysis, builds, integration/e2e checks, manual QA, and platform-specific checks. Run safe relevant checks when authorized.\n4. Review operational readiness: environment configuration, secrets handling, observability, error reporting, performance/capacity risk, backups, rollback path, and support/documentation impact.\n5. Identify blockers, high-risk unknowns, and deferred issues. Do not convert an uncertain condition into a release approval.\n\n## Final recommendation\n\nProvide a release-readiness table or concise list with each criterion, evidence, status, and owner/next action for gaps. End with one of: ready with evidence, conditionally ready with named conditions, or not ready with blockers. State exactly what remains to verify.\n\n"
}