dev-release

Name: dev-release
Availability: InStock
Author: Forecast

Coordinate branch creation, version bumps, changelogs, and GitHub releases.

27|3|Updated Mar 5, 2026

Search Tags:#automation #git #versioning #github #release #ci-cd #pull-request

Ready to run

npx skills add https://github.com/forecast-bio/ferray --skill dev-release-forecast-bio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-release
Source: https://github.com/forecast-bio/ferray/tree/main/.claude/skills/dev-release
Command: npx skills add https://github.com/forecast-bio/ferray --skill dev-release-forecast-bio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill acts as a release automation assistant that guides users through a complete software release lifecycle—from creating a release branch to publishing a GitHub release—balancing agent-driven steps with user-executed actions and enforcing policy constraints.

Core Features & Use Cases

Agent + user steps workflow: coordinates automated tasks (branch creation, version bumps, changelog drafting, and PR creation) while exposing safe, user-initiated steps (merge, tag, and final release decisions) with printed commands.
End-to-end release pipeline: supports multi-phase releases including version bump, changelog generation, docs review, tests & lint, PR creation, tag publishing, and back-merges.
Policy-aware safety: prints exact shell commands for user execution and blocks any disallowed operations to prevent unsafe actions.

Quick Start

Tell me to cut a release and specify the version to begin the guided release workflow.

Frequently Asked Questions about dev-release

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

FAQPage Schema

How do I automate GitHub release workflows with version bumps and changelogs?▼

Automate GitHub release workflows by coordinating branch creation, version bumps, changelog drafting, and PR creation in a guided pipeline. The process enforces a strict separation of agent-driven steps and user-performed actions, printing exact shell commands for safe execution.

What is a guided release pipeline that separates automated and manual steps?▼

A guided release pipeline coordinates automated tasks like branch creation, version bumps, and changelog generation while blocking unsafe operations. It reserves merge, tag, and final release decisions for the user, printing exact commands for manual execution to ensure policy-aware safety.

Can I use automated release workflows for multi-step pipelines including tests and lint?▼

Yes, automated release workflows support multi-phase pipelines including version bumps, documentation reviews, tests, lint execution, PR creation, tag publishing, and back-merges. The workflow coordinates these phases while enforcing policy constraints across each step.

How do I cut a release branch and create a GitHub release safely?▼

Cut a release branch by specifying the target version to initiate the guided workflow. The agent handles branch creation, version bumps, and changelog drafting, then prints exact shell commands for user-initiated merge, tag, and final release decisions to maintain safety.

Does automated release automation block unsafe operations during version bumps?▼

Yes, release automation blocks policy-violating actions by enforcing a strict separation between agent-driven steps and user-performed steps. It prints exact shell commands for user execution, preventing the agent from executing disallowed operations like merging or tagging directly.

What are the limitations of agent-driven release workflows for GitHub publishing?▼

Agent-driven release workflows cannot execute merge, tag, or final release decisions directly due to policy-aware safety constraints. Users must manually run the printed shell commands for these steps, meaning the workflow guides rather than fully automates the publishing process.