メニュー
Runs a short LEAP pre-merge release gate—CHANGELOG, migrations, docs touchpoints, lint, typecheck, tests. Use when the version bump and README narrative are already handled (e.g. via leap-version-bump) or for a quick final checklist before merge.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Reorganizes LEAP documentation—canonical locations, INDEX updates, superseded banners, archive vs dev_notes. Use when cleaning up docs, consolidating guides, marking files obsolete, or resolving duplicate how-tos.
Ships a product update: derives a short business summary from changed files, audits docs for stale version or mismatched behavior, bumps semver in pyproject/README/CHANGELOG and other stamped docs, then verifies with grep and make checks. Use when releasing, bumping version, updating README “what’s new”, or syncing docs after a feature merge.
Debugs stuck or failed LEAP recording pipelines—Celery queues, pipeline stages, and log correlation. Use when a recording fails mid-flight, a Celery task errors, workers seem idle, or the user asks to trace download through upload.
SOC 職業分類に基づく
| name | leap-release |
| description | Runs a short LEAP pre-merge release gate—CHANGELOG, migrations, docs touchpoints, lint, typecheck, tests. Use when the version bump and README narrative are already handled (e.g. via leap-version-bump) or for a quick final checklist before merge. |
For README narrative, exhaustive version grep, and doc freshness after a feature drop, prefer leap-version-bump first; this file stays a short merge checklist.
Follow workflow-changelog.mdc and alembic-migrations.mdc (project rules) for format details. Execute steps from backend/ unless noted.
Version
[project].version in backend/pyproject.toml (canonical).backend/api/__init__.py __version__, backend/config/settings.py version default, backend/.version, and root README.md v… lines to the same semver (full pass: leap-version-bump).Changelog
backend/docs/CHANGELOG.md entry: release header ## vX.Y.Z (YYYY-MM-DD) and/or dated sections per existing style.020) and deploy order if code and migrations must roll out together.Migrations (if any)
backend/alembic/versions/ uses 3-digit revision, matching filename {revision}_{slug}.py.make migrate: make db-version shows the expected revision; make db-history shows a linear chain to head (no stray multiple heads).Docs
backend/docs/TECHNICAL.md or backend/docs/guides/* if behavior, env vars, or operators’ steps changed (see table in workflow-changelog.mdc).backend/docs/INDEX.md if a new top-level doc was added.Verification
make lint and make typecheck from backend/.make test or at least make tests-mock if scope allows.Commit / PR