Coordinate XenonMAAS releases across npm, GitHub, and smoke testing.
npx skills add https://github.com/Joaoha/xenon-maas --skill release-joaoha
Please help me install this Agent Skill. Skill: release Source: https://github.com/Joaoha/xenon-maas/tree/main/.agents/skills/release Command: npx skills add https://github.com/Joaoha/xenon-maas --skill release-joaoha
Coordinate a full XenonMAAS release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up. Use when leadership asks to ship a release, not merely to discuss versioning.
release-changelogmasterscripts/docker-onboard-smoke.shTrigger the full XenonMAAS release workflow with a candidate source and target date.
High-intent search queries and answers about installing and using this skill.
Coordinate a full release by sequencing engineering verification, npm publishing, GitHub release creation, and Docker smoke testing. This workflow validates the repository state, drafts the changelog, publishes artifacts, and executes announcement follow-up tasks deterministically.
Canary promotion to stable works by taking a chosen source reference and executing a manual promotion sequence. The process verifies canary status from the master branch, validates inputs, and integrates release utilities to publish the stable version.
Automate changelog drafting by triggering the release-changelog utility during the deployment workflow. It validates the repository state and generates the changelog based on the provided source reference and target date inputs.
Yes, a dry-run input is supported for GitHub release automation. It allows you to validate the deterministic sequencing of release inputs and verify the repository state without publishing artifacts or creating the actual GitHub release.
Yes, you can run Docker smoke testing by executing the docker-onboard-smoke.sh script during the release workflow. It validates the published artifacts before proceeding to the GitHub release creation and announcement follow-up tasks.
Use a manual stable promotion when promoting from a specific canary source reference, rather than during a leadership-driven ship event. Manual promotion focuses on elevating a verified canary build to stable without triggering the full end-to-end release workflow.
priyansh19Coordinate CrewSpace release workflows from changelog drafting to GitHub release creation.
AEtherlight-aiAutomate ÆtherLight release publishing to npm and GitHub.
louisfbuysCoordinate Paperclip releases with changelog generation, Docker smoke testing, and GitHub Release creation.
sachinnair90Validate semver, token types, retries, and draft-release triggers in GitHub Actions publish workflows.