菜单
Manage qrypt version releases: cut tags, trigger CI builds, inspect release artifacts. Use when the user asks to release a new version, cut a tag, publish a release, or check CI release status.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Architecture-oriented code health maintenance for the qrypt project. Use when asked to audit code, review technical debt, improve consistency, or clean up architecture drift. The skill may either report findings or make focused code changes when the evidence is strong.
Periodic code health maintenance for the qrypt project. Scans the codebase for naming inconsistencies, duplicated code, package structure issues, and domain concept drift. Generates a structured report with fix suggestions. Use when the user asks to audit code, review code health, run maintenance, check for technical debt, or enforce coding conventions.
Migrate storage drivers from OpenList/OpenListTeam implementations into the qrypt Go codebase. Use when Codex is asked to add a new qrypt driver based on OpenList source code, port an OpenList cloud drive API implementation, compare OpenList driver behavior with qrypt driver contracts, or debug a partially migrated qrypt driver for list/read/write/path/config/schema/cache/staging behavior.
Migrate storage drivers from OpenList/OpenListTeam implementations into the qrypt Go codebase. Use when Codex is asked to add a new qrypt driver based on OpenList source code, port an OpenList cloud drive API implementation, compare OpenList driver behavior with qrypt driver contracts, or debug a partially migrated qrypt driver for list/read/write/path/config/schema/cache/staging behavior.
| name | qrypt-release |
| description | Manage qrypt version releases: cut tags, trigger CI builds, inspect release artifacts. Use when the user asks to release a new version, cut a tag, publish a release, or check CI release status. |
feat/* branch is merged into main.git tag v0.1.0
git push origin v0.1.0
check: runs vet and tests before release builds.dist-linux-windows: builds Linux binaries with Docker and Windows binaries with nocgo cross-compilation, then packages release archives.dist-darwin: builds macOS binaries on macOS with macFUSE installed, then packages release archives.release: downloads packaged archives, then GoReleaser publishes GitHub Release assets, checksums, and changelog.Release assets are packaged before GoReleaser runs. .goreleaser.yaml uses builds.skip: true and release.extra_files, so GoReleaser is only responsible for publishing prebuilt archives, generating checksums, and generating release notes.
| Target | Method | Deps |
|---|---|---|
linux/amd64 | Docker + fuse-dev | Docker |
linux/arm64 | Docker + fuse-dev on ubuntu-24.04-arm | Docker |
windows/amd64 | nocgo cross-compile | Go only |
windows/arm64 | nocgo cross-compile | Go only |
darwin/amd64 | native go build + FUSE | macOS |
darwin/arm64 | native go build + FUSE | macOS |
Windows builds use CGO_ENABLED=0 -tags nocgo. They still require users to install WinFSP at runtime for mount support; nocgo only removes the CI dependency on mingw and WinFSP headers.
Expected GitHub Release assets:
qrypt_<version>_linux_amd64.tar.gzqrypt_<version>_linux_arm64.tar.gzqrypt_<version>_darwin_amd64.tar.gzqrypt_<version>_darwin_arm64.tar.gzqrypt_<version>_windows_amd64.zipqrypt_<version>_windows_arm64.zipqrypt_<version>_checksums.txtIf a release only contains GitHub's default source archives, check that:
dist/*.tar.gz and dist/*.zip.dist/..goreleaser.yaml has matching release.extra_files and checksum.extra_files globs.GITHUB_TOKEN: ${{ secrets.GH_TOKEN }} and has contents: write permission.The release config uses replace_existing_artifacts: true, so rerunning the same tag can replace uploaded assets.
# List recent runs
gh run list --limit 5
# View workflow status
gh run view <run-id>
# View failed job logs
gh run view <run-id> --log-failed
v0.0.1, v0.1.0, v1.0.0 — semantic versioningv to trigger CI (tags: [v*] in CI config)feat:, fix:) grouped by type