Prompt file imported from itz4blitz/ai-tools (.codex/prompts/release-prep.md). Copyright stays with the author.

Prepare for release

Name: release-prep
Author: itz4blitz

Verify the codebase is ready for semantic-release on merge to master.

Steps

Run npm run check — all four stages must pass (lint, format, typecheck, test)
Check recent commits follow conventional commit format (Angular preset):
- feat: → minor release
- fix:, perf:, refactor:, revert: → patch release
- docs:, chore:, style:, test:, ci: → no release
- BREAKING CHANGE: in footer → major release
Run npm run release:publish:dry to preview the @itz4blitz/ai-tools publish
Verify all internal workspace package.json files remain private implementation details and stay version-aligned with packages/cli/package.json
Check that scripts/sync-versions.js, scripts/vendor-cli-bundle.js, scripts/clean-cli-bundle.js, and scripts/run-semantic-release.js are intact and unmodified
If @itz4blitz/ai-tools has never been published before, ensure a one-time NPM_TOKEN secret is available for the bootstrap release. After the first publish, trusted publishing via OIDC should handle future releases.

Report the results: whether @itz4blitz/ai-tools is ready to publish, what version bump is expected, and any repo-side or npm-side blockers.

{ "prompt": "# Prepare for release\n\nVerify the codebase is ready for semantic-release on merge to master.\n\n## Steps\n\n1. Run `npm run check` — all four stages must pass (lint, format, typecheck, test)\n\n2. Check recent commits follow conventional commit format (Angular preset):\n - `feat:` → minor release\n - `fix:`, `perf:`, `refactor:`, `revert:` → patch release\n - `docs:`, `chore:`, `style:`, `test:`, `ci:` → no release\n - `BREAKING CHANGE:` in footer → major release\n\n3. Run `npm run release:publish:dry` to preview the `@itz4blitz/ai-tools` publish\n\n4. Verify all internal workspace `package.json` files remain private implementation details and stay version-aligned with `packages/cli/package.json`\n\n5. Check that `scripts/sync-versions.js`, `scripts/vendor-cli-bundle.js`, `scripts/clean-cli-bundle.js`, and `scripts/run-semantic-release.js` are intact and unmodified\n\n6. If `@itz4blitz/ai-tools` has never been published before, ensure a one-time `NPM_TOKEN` secret is available for the bootstrap release. After the first publish, trusted publishing via OIDC should handle future releases.\n\nReport the results: whether `@itz4blitz/ai-tools` is ready to publish, what version bump is expected, and any repo-side or npm-side blockers.", "variables": [], "notes": "Verify the codebase is ready for semantic-release on merge to master.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/itz4blitz/ai-tools", "path": ".codex/prompts/release-prep.md", "ref": "494e0ba6c8eba5721a137e1fe7f6270159dd3fcf", "url": "https://github.com/itz4blitz/ai-tools/blob/494e0ba6c8eba5721a137e1fe7f6270159dd3fcf/.codex/prompts/release-prep.md", "key": "itz4blitz/ai-tools/.codex/prompts/release-prep.md" } } }

release-prep

About

Prepare for release

Steps

Use it

Manifest

Reviews