메뉴
Prepare a qsv release by bumping versions across all files and updating changelog
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Standard workflow order, tool selection matrix, and composition patterns for qsv CSV data wrangling
Respond to all pending review comments on the current PR — fetch comments, apply fixes, verify accuracy, test, commit, and reply. Use when addressing Copilot reviews, GitHub PR reviews, or any batch of review feedback.
Prepare an MCP server and plugin release by bumping versions across all files and updating changelog
Run SQL queries against CSV/TSV/Excel files using Polars SQL engine
Clean a CSV/TSV/Excel file - fix headers, trim whitespace, remove duplicates, validate
Convert between CSV, TSV, Excel, JSONL, Parquet, and other tabular formats
| name | release-prep |
| description | Prepare a qsv release by bumping versions across all files and updating changelog |
| disable-model-invocation | true |
Prepare a qsv release by updating version numbers across all required files and generating a changelog entry.
version (required): The new version number (e.g., "16.2.0")msrv (optional): New minimum supported Rust version, if changingUpdate the version string in ALL of these files:
Cargo.toml (line 3): version = "X.Y.Z"CLAUDE.md: **Current Version**: X.Y.Z in Project Overview.claude/skills/manifest.json: "version" field (MCP server version -- may differ from binary version).claude/skills/package.json: "version" field (must match manifest.json)CHANGELOG.md: Add new version section at topIf MSRV is changing, also update:
6. Cargo.toml (line 15): rust-version = "X.Y"
7. CLAUDE.md: **MSRV**: Rust X.Y in Project Overview
Add a new section at the top of CHANGELOG.md following this format:
## [X.Y.Z] - YYYY-MM-DD
### Added
- (new features)
### Changed
- (changes to existing features)
### Fixed
- (bug fixes)
### Removed
- (removed features)
Use git log from the last release tag to populate the changelog sections.
Exclude commits with (mcp) or (plugin) in the title — those belong in the MCP/Plugin changelog (.claude/skills/CHANGELOG.md) and are handled by /mcp-release-prep.
Add links to relevant PRs and issues for each changelog entry when possible.
After version bumps, remind the user to:
cargo build --locked --bin qsv -F all_features to verify the build (omit --locked if deps changed)cargo test -F all_features to verify tests passqsv --update-mcp-skills to regenerate skill JSONs with new versionbash contrib/completions/generate_examples.bash to regenerate completionscargo +nightly fmt to format any changed Rust filesmanifest.json/package.json can advance independently of the qsv binary versionminimum_qsv_version field in manifest.json tracks the minimum qsv binary needed, NOT the MCP server versionCargo.toml version, omit --locked from cargo commands until Cargo.lock is regenerated