Automates versioned releases of the dev-ready package from version bump to PyPI publish.
npx skills add https://github.com/MoofonLi/dev-ready --skill release-moofonli
Please help me install this Agent Skill. Skill: release Source: https://github.com/MoofonLi/dev-ready/tree/main/.agents/skills/release Command: npx skills add https://github.com/MoofonLi/dev-ready --skill release-moofonli
src/dev_ready/__init__.py, pyproject.toml, .claude-plugin/plugin.json, .codex-plugin/plugin.json) plus uv.lock so the CLI, wheel, and plugin manifests never disagree. - Gated verification and documentation: Runs unit, lint, and network-marked integration tests before allowing a release, then guides writing the docs/version_overview/<version>-overview.md record and a doc status sweep. - Staged commits, CI gating, and tagging: Groups changes into Conventional Commits, waits for all six CI jobs to pass, then tags and pushes to trigger the release.yml PyPI publish, with troubleshooting for failed CI, stale git locks, and tag/version mismatches. - Use Case: After finishing a development phase, tell your agent "release v0.3.0" and it will bump versions, verify everything, prepare the overview and commit commands, and walk you through tagging and publishing. ## Quick Start Ask your agent to release version X.Y.Z of the dev-ready repo, for example by saying "release v0.3.0", and follow the gated steps it prepares.High-intent search queries and answers about installing and using this skill.
State the target version (e.g. "release v0.3.0") and follow the gated workflow: bump the version in four files, run pytest and ruff locally, write the version overview, stage Conventional Commits, push, wait for all six CI jobs, then tag and push the tag to trigger PyPI publishing.
Update all four version locations together: src/dev_ready/__init__.py, pyproject.toml, .claude-plugin/plugin.json, and .codex-plugin/plugin.json. The CLI prints __version__ while the release workflow validates the tag against pyproject.toml, so any mismatch ships a CLI reporting the wrong version.
Fix the problem, commit it, then delete the local and remote tag, re-tag the fixed commit, and push again to re-trigger the release pipeline. This is only safe before PyPI publishes; if the version already published, release the next patch version instead.
release.yml refuses to publish when the pushed tag does not match the version in pyproject.toml. Fix the version files, commit the correction, and re-tag with the matching vX.Y.Z tag before pushing again.
The lock file remains after a git process died, often following an editor or agent crash. Confirm no git process is running, then delete .git/index.lock (del on Windows, rm -f on macOS/Linux) and retry the command.
No, PyPI rejects re-uploading a version that already published. If PyPI already has X.Y.Z, do not re-tag; bump to X.Y.Z+1 and release that instead. If only the GitHub Release step failed, create it manually with gh release create.
taxmaxiImplement code changes from a spec or tickets using TDD and code review.
peeka-projectAutomate versioning, commit, tag, and push for GitHub releases.
alvisRestructure passing code to improve naming, readability, and documentation without changing behavior.
mia-cxAutomate software releases with versioning, changelog generation, and GitHub releases.