Solo Maintainer Release
SkillDocs & knowledgeRuns solo-maintainer release work end-to-end: release readiness review, notes, tags, GitHub release creation, deploy workflow dispatch, and post-release verification. Auto-executes unless the shared suspicious-change policy is triggered.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Solo Maintainer Release skill
What this skill tells your AI
The instructions your AI receives, as published by serithemage/serverless-openclaw in .agents/skills/solo-maintainer-release/SKILL.md and read by ahel’s review.
Required Context
Read these first:
Release Flow
- Verify the release candidate is not blocked by suspicious pending changes.
- Run the local release gate:
npm run checknpm run buildnpm run web:buildnpm run testnpm run test:e2e
- Run integration tests when the required live environment variables exist.
- Update or confirm release notes and changelog entries before tagging.
- Create the tag and GitHub release only after the evidence is collected.
- If the request includes deployment, dispatch the relevant workflow with
gh workflow run, monitor it, and handle environment approval when expected and safe. - After deployment, verify the run result and note any follow-up cleanup.
Parallelism Rule
- If the platform supports subagents or workers, parallelize independent review lanes.
- If not, run the same lanes sequentially and keep a compact approval or reject note for each lane.
Stop Conditions
- Any suspicious-change signal from the shared policy
- failed verification that changes release safety
- unexplained drift between release notes and shipped behavior
Signals
- GitHub stars
- 195
- Forks
- 40
- Last commit
- Mar 2026
Advanced
- Catalog kind
- skill
- Gateway key
solo-maintainer-release- Source
- github.com/serithemage/serverless-openclaw