Automate the Otto bridge release workflow with commits, pushes, CI checks, and host upgrades.
npx skills add https://github.com/otto-assistant/bridge --skill otto-publish
Please help me install this Agent Skill. Skill: otto-publish Source: https://github.com/otto-assistant/bridge/tree/main/skills/otto-publish Command: npx skills add https://github.com/otto-assistant/bridge --skill otto-publish
This skill automates the end-to-end Otto release workflow, handling commits, pushes, CI verification, host upgrades, and restarting dependent services to publish new versions.
Run the CLI and follow the interactive prompts to publish Otto.
High-intent search queries and answers about installing and using this skill.
Automating a release workflow with GitHub Actions and npm publish involves coordinating git commits, CI checks, and host upgrades. This skill orchestrates the full cycle, triggering workflows and validating the new npm version on the host.
An end-to-end bridge release workflow handles versioning, git pushes, CI verification, npm publishing, and host upgrades. It coordinates these steps to ensure dependent services restart with the latest verified code.
To verify a published npm version and restart dependent services, you validate the new version on the host after CI checks pass. This skill confirms running processes match the latest code and reports success with evidence.
Yes, GitHub Actions must be configured to automate the npm release process. The workflow triggers existing GitHub Actions workflows to execute CI checks and validate the release before upgrading the host.
The best way to coordinate versioning and CI checks for a release is using an orchestration workflow that automates commits, triggers GitHub Actions, and validates the published version on the host with final verification evidence.
raphaelchristiAutomate npm package releases with changelog generation and GitHub publishing.
manastalukdarPoll logs, error rates, and endpoints to verify post-deployment health.
andymaiCoordinate software package releases to the npm registry and web interfaces.
vecearAutomate releases, changelogs, git tags, and npm publishing with changesets or semantic-release.
