菜单
Prepare, verify, and audit pqforge releases. Use when changing the package version, updating release notes, preparing a release branch or tag, checking the pub.dev archive, validating generated version/visibility files, building release binaries, or publishing to pub.dev/GitHub.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Maintain pqforge documentation in lockstep with the code, with zero hallucinated APIs, commands, numbers, or links. Use whenever editing README.md, CHANGELOG.md, anything under doc/ or wiki/, the visibility manifest (tool/visibility/visibility_manifest.json), the generator, or any generated AI-discovery file (llms.txt, llms-full.txt, identity.json, faq-ai.txt, developer-ai.txt, ai.txt, robots*.txt, site/**, .github/copilot-instructions.md, .github/instructions/**, .cursor/rules/**, .windsurfrules). Enforces the verify-against-code protocol, the generated-vs-hand-maintained split, the claim boundary, the main-branch link rule, and the regenerate-and-validate checklist.
Implement pqforge library, CLI, codec, recipe, streaming, hybrid, custody, test, or example features. Use for behavior changes under lib/**, bin/**, example/**, or test/** and for cross-cutting feature refactors.
Prepare and verify pqforge package releases. Use for version changes, changelog release notes, pub.dev archive checks, release branches, tags, GitHub binaries, or pub.dev publication.
Maintain pqforge documentation from live code evidence. Use when editing README.md, CHANGELOG.md, CLAUDE.md, AGENTS.md, doc/**, wiki/**, the visibility manifest or generator, generated AI-discovery/editor files, or site/**. Also use when verifying API names, CLI commands, flags, performance numbers, package claims, links, or generated-document consistency.
Implement pqforge features and fixes across the library, CLI, codecs, recipes, streaming, hybrid cryptography, key custody, tests, and examples. Use for any behavior change under lib/**, bin/**, example/**, or test/**, including new APIs, commands, flags, formats, cipher/provider behavior, performance changes, and cross-cutting refactors.
| name | pqforge-release |
| description | Prepare, verify, and audit pqforge releases. Use when changing the package version, updating release notes, preparing a release branch or tag, checking the pub.dev archive, validating generated version/visibility files, building release binaries, or publishing to pub.dev/GitHub. |
git status,
pubspec.yaml, the top of CHANGELOG.md, and existing tags.pubspec.yaml and CHANGELOG.md together. Do not infer the version
from a manifest or generated file.dart run tool/version/generate_version.dart
dart run tool/visibility/generate_visibility.dart
$pqforge-docs..pubignore still limits the archive to the runtime package.Run the full release gate from a clean checkout:
dart pub get
dart pub get --directory tool/openssl_interop
dart run tool/agent/verify.dart release
Run the OpenSSL interop and streaming memory gates when affected. Compile and smoke-test the CLI if release-binary behavior changed.
The strict archive check must have zero warnings. Never hide warnings with
--ignore-warnings for an actual release.
v<version> tag only for the exact published commit.Read doc/ci/RELEASE_CHECKLIST.md for the repository checklist.