code-review
Review source changes for defects.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- code-review
- description
- Review source changes for defects.
02 资源文件 1
- 参考文档agents/openai.yaml282 B
03 SKILL.md 正文
该 Skill 的授权仅允许展示来源链接,正文请前往 GitHub 查看。
查看 SKILL.md ↗04 同仓库更多 Skills
code-review
Review source changes for defects.
releasing-apss
Use when cutting, gating, tagging, or publishing a release of this APSS repo, or when explaining how releases work here. Trigger phrases: "cut a release", "release APSS", "publish to crates.io", "create a release PR", "main to release", "promote main to release", "bump versions for the release", "tag a release", "run the release gate", "how do releases work here", "what gets published", "ship a new version", "publish a new crate for the first time", "403 Forbidden publishing to crates.io", "this token does not have the required permissions", "CARGO_REGISTRY_TOKEN", "publish-new scope", "the publish job failed", "half the crates published". Covers the trunk-based main -> release branch flow, the Release Gate checks (source-branch, version-bump, changelog, QA, APS validation, security), release-create.yml tagging plus tiered crates.io publishing, and the one-time manual first publish a NEW crate name requires because the CI token is deliberately scoped publish-update only. Do NOT use for routine feature PRs into main (those need no release and no version bump), mid-feature version bumps, authoring standards, or consumer-side `apss install` (see the adopt/visualize runbooks).