Menú
Complete release workflow from version prep through PyPI publication
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Get Neo's architectural guidance for design decisions. Trade-off analysis for choices like microservices vs monolith, sync vs async, event-driven vs request-response — with persistent memory of how similar decisions played out.
Ask Neo to help debug intermittent, complex, or hard-to-reproduce issues. Particularly useful for race conditions, memory issues, distributed-systems bugs, and cases where the symptom is not the root cause.
Ask Neo for optimization suggestions on a function, file, or hot path. Targets algorithmic improvements, redundant work, allocation/hot-loop issues — not micro-style.
Ask Neo to extract a reusable pattern from a piece of code, or to find existing patterns in the codebase that match a description. Useful for codifying conventions and finding duplicated logic.
Get Neo's code review with semantic pattern matching. Focuses on security vulnerabilities, edge cases, error handling, and performance issues across the target file or module.
Ask Neo for semantic reasoning and code suggestions over the current codebase. Use for general questions, code suggestions, or architectural guidance backed by Neo's persistent memory.
| name | source-command-ship-release |
| description | Complete release workflow from version prep through PyPI publication |
Use this skill when the user asks to run the migrated source command ship-release.
Orchestrates the full release workflow: version prep, PR creation, tagging, and PyPI publication.
/ship-release 0.7.7
Runs the complete release workflow for projects with protected main branches:
/prepare-release to update versions and changelogrelease/v{version})Run /prepare-release {version} which:
importlib.metadata.version("neo-reasoner") == "{version}"git checkout -b release/v{version}
If branch already exists, check it out instead.
git add CHANGELOG.md pyproject.toml src/neo/__init__.py .claude-plugin/plugin.json plugins/neo/.codex-plugin/plugin.json
git commit -m "chore: bump version to {version}"
git push origin release/v{version}
gh pr create --title "Release v{version}" --body "<changelog summary>"
CHECKPOINT: Command stops here. Report PR URL and next steps.
User must:
python -c "import importlib.metadata as m; print(m.version('neo-reasoner'))"Then run: /ship-release {version} --continue
git checkout main
git pull origin main
git tag v{version}
git push origin v{version}
gh release create v{version} \
--title "v{version}" \
--notes "<changelog content>" \
dist/neo_reasoner-{version}*
This triggers the GitHub Actions workflow (.github/workflows/publish.yml) which publishes to PyPI.
Check that:
Report status and provide link to new release.
--continue: Resume after PR is merged (skips phases 1-4)--dry-run: Show what would happen without making changesIf PR creation fails: Check if PR already exists, provide URL if so
If tag already exists: Report conflict, suggest incrementing version
If GitHub Actions fails: Check workflow logs at github.com/{repo}/actions
If PyPI publish fails: Check Actions logs for authentication or build issues
gh CLI authenticated with GitHub/prepare-release alone if you just want to prep without full release