devops-cut-boring-ui-release

Automate boring-ui CLI release lifecycle with versioning, npm publication, and systemd restarts.

45|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/hachej/boring-ui --skill devops-cut-boring-ui-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devops-cut-boring-ui-release
Source: https://github.com/hachej/boring-ui/tree/main/.agents/skill-library/devops-cut-boring-ui-release
Command: npx skills add https://github.com/hachej/boring-ui --skill devops-cut-boring-ui-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates the complex, multi-step process of cutting a new boring-ui release, ensuring consistency across GitHub, npm, and local global installations while minimizing downtime.

Core Features & Use Cases

  • Automated Release Pipeline: Handles version bumping, git tagging, and GitHub release creation.
  • Global CLI Synchronization: Automatically updates the global npm package and restarts systemd-managed workspace services.
  • Verification Gates: Performs automated linting, type checking, and testing before publication to ensure stability.

Quick Start

Ask the agent to cut a new boring-ui release and update the global CLI installation on this machine.

Frequently Asked Questions about devops-cut-boring-ui-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate npm CLI release and global package synchronization?

Automating npm CLI release handles version bumping, git tagging, and npm publication while automatically updating global installations. It ensures consistency across GitHub, npm, and local environments while minimizing downtime.

What's the best way to cut a new release for a CLI using git worktrees and systemd?

Cutting a CLI release using git worktrees and systemd automates the end-to-end lifecycle by managing worktrees, validating build gates, and performing zero-downtime service restarts within the repository.

Do I need GitHub CLI and systemd access to automate boring-ui deployment?

Yes, you need GitHub CLI, npm, and systemd access to execute deployment and verification tasks. These tools are required to manage the release pipeline and perform global environment synchronization.

How does automated release validation prevent broken npm publications?

Automated release validation prevents broken npm publications by performing verification gates before publication. It runs automated linting, type checking, and testing to ensure package stability before deploying.

Can I use this to perform zero-downtime service restarts for global CLI updates?

Yes, it performs zero-downtime service restarts for global CLI updates by synchronizing the global npm package and restarting systemd-managed workspace services automatically after a successful publication.