// Prepares and automates the release process for multi-storage-client (version bump, release notes, checklist). Use when the user wants to cut a release, bump version, prepare release, publish a new version, or automate release steps.
Append a learning to agent-learnings.md when the agent or user identifies a mistake, non-obvious pattern, or useful convention worth remembering. Use when the user says "capture this", "remember this", or "add to learnings".
Set up MSC credentials and MCP server integration for cloud storage access. Use when the user wants to interact with cloud storage (S3, GCS, Azure, OCI), asks to set up credentials, connect to a bucket, list objects, move files, or sync data. Checks for existing config first — only runs interactive setup if credentials are missing.
Fix CVE vulnerabilities by upgrading affected dependencies across Python (uv), Go, and Rust layers. Use when the user mentions CVE numbers, asks to fix security vulnerabilities, or asks to patch dependencies for CVEs.
Produce a feature specification covering API changes, backward compatibility, cross-language impact, performance, and a file-level change plan. Use when designing a new feature, planning a significant change, or the user asks to spec something out.
Produce a test plan with specific test names, assertions, and coverage across Python, Rust, and Go. Use when planning tests for a feature, after generating a spec, or the user asks for a test plan.
Stage files, commit with correct format, push, and generate an MR description. Manual invocation only — has side effects (git operations). Use when the user explicitly asks to prepare, create, or submit an MR.
| name | release-automation |
| description | Prepares and automates the release process for multi-storage-client (version bump, release notes, checklist). Use when the user wants to cut a release, bump version, prepare release, publish a new version, or automate release steps. |
Guides the agent through preparing a release for the multi-storage-client repository. Tagging is done by the pipeline after the release MR is merged; this skill covers only the in-repo changes (version bump, release notes). Do not ask the user to run git tag or push a tag.
.release_notes/.unreleased.md has been updated with notable changes (per PR template). If empty or placeholder-only, confirm with the user before releasing.multi-storage-client/pyproject.toml (version = "X.Y.Z").multi-storage-client/pyproject.toml, set version = "<new_version>" (e.g. "0.44.0")..release_notes/.unreleased.md.git log <previous_version>..HEAD --no-merges --format='%h %s%n%b' (tags are unprefixed, e.g. 0.42.0 not v0.42.0). Use this to find and add relevant entries; omit CI/CD, build, and chore-only commits..release_notes/<new_version>.md with that content (e.g. .release_notes/0.44.0.md). Preserve structure (Breaking Changes, New Features, Bug Fixes, etc.). Split into Multi-Storage Client (MSC) and Multi-Storage File System (MSFS) sections when changes span both sub-projects..release_notes/.unreleased.md to its template (the section headings under MSC and MSFS with <!-- Add items here. --> at the top). If unsure whether the repo convention expects a reset, ask the user before modifying.just build from repo root (runs analyze, unit tests, ray tests; in CI also runs package).Present a short checklist for the user:
multi-storage-client/pyproject.toml..release_notes/<new_version>.md created; .release_notes/.unreleased.md handled as above.just build passed (or user will run locally).