Verifies ocmm release completion through a fail-closed checker across tags, workflow runs, and release assets.
npx skills add https://github.com/hugefiver/ocmm --skill publish-hugefiver
Please help me install this Agent Skill. Skill: publish Source: https://github.com/hugefiver/ocmm/tree/main/plugins/deepwork/skills/publish Command: npx skills add https://github.com/hugefiver/ocmm --skill publish-hugefiver
pnpm --silent run check:release-completion and requires a JSON receipt with outcome: "COMPLETED" binding the exact tag, peeled commit SHA, fixed workflow run and attempt, lane-correct job conclusions, and verified SHA-256 assets. - Ship-Only Guardrails: Prohibits code repairs, tag mutation, registry overwrites, or fix loops during publishing; repairs require a separately authorized commit and new tag. - Structured Outcome Handling: Defines exact reporting behavior for COMPLETED, FAILED, and UNRESOLVED outcomes, including partial-surface reporting and safe resumption of proof without moving the immutable tag. - Use Case: After pushing tag v0.6.6 for the ocmm package, invoke this Skill to run the completion checker against the release.yml run and confirm the GitHub Release assets and checksums before announcing the release. ## Quick Start Authorize an ocmm release and ask the agent to publish tag v0.6.6, then verify completion with the release-completion checker.High-intent search queries and answers about installing and using this skill.
Run `pnpm --silent run check:release-completion` with the tag, repository, and deadline parameters from the released checkout. The release is complete only when it exits 0 with a JSON receipt showing outcome COMPLETED covering the tag, run, assets, and checksums.
A terminal workflow success only shows jobs finished, not that every publication surface landed. The completion contract requires proof of the exact tag, peeled commit, fixed run attempt, lane-correct job conclusions, non-empty Release assets, and verified SHA-256 checksums.
No. The tag is immutable once publication starts and must never be moved, deleted, or recreated. A repair requires a separately authorized normal commit with a new version and tag, or an explicitly authorized workflow rerun preserving the same tag identity.
Report every required non-registry surface lacking proof plus the retained tag, SHA, run ID, and attempt, and identify whether the cause is propagation, retryable network state, or deadline. A later checker rerun can resume proof without changing the tag.
No local GITHUB_TOKEN is needed to bump, tag, push, or trigger CI. The checker does not query npmjs or GitHub Packages, while registry publication continues inside the workflow with workflow-managed authentication.
skaile-aiAutomate changelog generation, version bumps, and annotated git tags for releases.
AO-Cyber-SystemsArchive completed milestones and create Git tags for released versions.
dwertentDiagnose GitHub Actions CI failures from run URLs and propose fixes.
kortix-aiAutomates Kortix production releases from git log through promote, deploy, and verification.