---
description: Prepare pi-ext release readiness checklist
argument-hint: "[extension|all] [flags]"
---

# Prepare pi-ext release readiness checklist

Prepare pi-ext release readiness for `$ARGUMENTS`.

Goal:
verify release, do not publish.
Tie check/readme/dry-run together.

Rules:

- Do not commit, tag, push, or publish unless user explicitly says OK after
  report.
- Prefer jj if `jj root` succeeds; otherwise git.
- Stop on unrelated dirty changes, failing checks, missing READMEs,
  or ambiguous release scope.
- Use existing changed-since-release behavior; do not regenerate unchanged READMEs unless the user asks.

Workflow:

1. Inspect state:
   - `jj status` else `git status --short --branch`
   - `mise tasks ls`
   - read `mise.toml` and `scripts/extensions.mjs` if release flow looks stale
2. Scope:
   - Determine target extension(s) from `$ARGUMENTS`; empty/all means all.
   - Determine changed extensions since latest release tag.
3. Check:
   - `mise run build -- <extension>` for one extension.
   - `mise run ci` for all/multi-extension release.
4. README:
   - `mise run readme`
   - Verify generated README diffs only touch intended files.
5. Dry run:
   - `mise run publish -- --dry-run --no-push`
   - Verify version, README/changelog text, selected extensions.
6. Report:
   - READY | NOT READY
   - scope
   - checks run
   - readmes updated/skipped
   - dry-run outcome
   - exact publish command to run after OK

Output terse.
Include blockers first.