Menu
Prepare and publish a PyPI release - version bump, changelog, tag, publish
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Pre-release docs sync — diff HEAD against the last v* tag on the publish remote, list feature additions, update README language/tool inventory, draft the CHANGELOG release entry, propose the version bump. Runs before /release. Prevents shipping with stale docs.
Weekly documentation refresh and maintenance - audit staleness, update docs, validate backlog
Scan codebase for AI-generated entropy — duplicated helpers, dead code, spreading anti-patterns. Use on a regular cleanup cadence or when noticing quality drift.
Automate the repository post-implementation hardening workflow, including optional Codex diff review with returned comments
Plan implementation for a backlog task with mode classification and optional Codex review
Smart verification — detects what changed and runs appropriate tests, lint, typecheck
| name | release |
| description | Prepare and publish a PyPI release - version bump, changelog, tag, publish |
| disable-model-invocation | false |
Prepare and optionally publish a new version to PyPI.
Run /verify to ensure all tests pass.
Check current version:
grep -E "^version\s*=" pyproject.toml
git tag --list 'v*' | tail -5
Based on changes since last release:
| Change Type | Version Bump |
|---|---|
| Breaking changes (API, CLI, storage format) | Major (X.0.0) |
| New features (languages, MCP tools) | Minor (0.X.0) |
| Bug fixes, docs, internal | Patch (0.0.X) |
Ask user to confirm version if unclear.
Edit pyproject.toml:
# Example: bump to 1.1.0
sed -i '' 's/^version = .*/version = "1.1.0"/' pyproject.toml
Add entry to CHANGELOG.md with today's date:
## vX.Y.Z — YYYY-MM-DD
### Added
- ...
### Fixed
- ...
### Changed
- ...
git add pyproject.toml CHANGELOG.md
git commit -m "chore: release vX.Y.Z"
git tag -a vX.Y.Z -m "Release vX.Y.Z"
Ask user before pushing:
Ready to push release vX.Y.Z to origin?
- git push origin main
- git push origin vX.Y.Z
Proceed? [y/n]
Ask user before publishing:
Ready to publish vX.Y.Z to PyPI?
- Requires: TWINE_USERNAME/TWINE_PASSWORD or ~/.pypirc
Command: python -m build && twine upload dist/*
Proceed? [y/n]
If user confirms:
rm -rf dist/ build/
python -m build
twine upload dist/* --repository publish
Note: Uses publish remote per project feedback.
## Release vX.Y.Z
Version: X.Y.Z
Tag: vX.Y.Z
Pushed: [yes/no]
Published: [yes/no/skipped]
Next steps:
- [any remaining manual steps]