chore: add a shared release skill and candidate verifier - #302
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.agents/skills/releaseskill with phase guides, discoverable throughAGENTS.md. Remove the standaloneRELEASE.mdso release managers and agents use the same maintained procedure.release_verifierfor independent checks of existing candidate artifacts. It follows the shared verification guide and returns evidence; the main agent coordinates publication and the existing license-audit capability handles licensing.Validation:
cargo x lint, skill validation, local links and table alignment, shell example syntax, and ASF headers. A native Codex run dispatched the configured verifier against two local signed archive fixtures: the matching archive passed, and an archive with a modified README was identified despite valid signatures and checksums. This smoke test covered candidate identity and source verification; it did not build, package, or publish a release.