goal-release

Automate version bumping, pull requests, CI verification, and npm publication.

1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/dyoshikawa/webseek --skill goal-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: goal-release
Source: https://github.com/dyoshikawa/webseek/tree/main/.rulesync/skills/goal-release
Command: npx skills add https://github.com/dyoshikawa/webseek --skill goal-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual overhead and potential for human error in the software release process by orchestrating the entire lifecycle from drafting to publishing.

Core Features & Use Cases

  • Automated Release Orchestration: Handles version bumping, PR creation, CI monitoring, merging, and final publication.
  • Safety Guardrails: Enforces CI pass requirements and prevents merging if unexpected commits or configuration changes are detected.
  • Use Case: Use this when you are ready to ship a new version and want the AI to handle the release PR, verify the build, and ensure the package is published to npm without manual intervention.

Quick Start

Use the goal-release skill to automatically draft, verify, and publish the next version of the project.

Frequently Asked Questions about goal-release

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

FAQPage Schema
How do I automate npm package releases with GitHub and CI/CD workflows?

You can automate npm package releases by orchestrating version bumping, PR creation, CI monitoring, and publication. This approach requires GitHub CLI integration and configured CI/CD workflows to ensure secure, verified deployments without manual intervention.

What is automated release orchestration for software maintenance workflows?

Automated release orchestration handles the end-to-end software release lifecycle from drafting to publishing. It manages version bumping, pull request creation, CI verification, merging, and final package publication to maintain consistent release cycles.

Do I need GitHub CLI to automate end-to-end software releases?

Yes, GitHub CLI integration is required to automate end-to-end software releases. You also need configured CI/CD workflows to enforce safety guardrails, verify builds, and ensure reliable package publication.

How do I prevent merging a release PR if CI checks fail?

You can prevent merging by using safety guardrails that enforce CI pass requirements. The automation blocks merges if unexpected commits or configuration changes are detected, ensuring only verified builds are published.

Can I publish to npm without manual intervention after creating a release PR?

Yes, the automation handles the entire lifecycle from drafting the release PR to publishing the package. It monitors CI checks, merges the verified PR, and publishes to npm automatically once safety guardrails pass.