Release Notes Journal for Openclaw

Turn a structured release change set into a concise release-note receipt and a local business artifact.

wxt-ai
v1.1.1
Oct 5, 2026
0
356
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install repository-release-changes-workbench

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install repository-release-changes-workbench using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Release Notes Journal?

Release Notes Journal is an Openclaw Skills workflow for routine release coordination when you need to publish a release-note entry. It accepts a prepared change set and returns a receipt containing the change identifier, title, Markdown release note, and file count.

The skill runs locally without credentials or access to private files. It writes an artifact beneath the output directory you specify; if delivery is configured, it can also perform the declared send, registration, or submission action and return a delivery receipt.

Release Notes Journal Use Cases

  • Prepare a release-note entry from a structured release handoff.
  • Generate a concise receipt for a change set before or during release coordination.
  • Record a release artifact locally when no external delivery target is configured.
  • Send, register, or submit a release record when an appropriate delivery target is configured.

How Release Notes Journal Works

  1. Provide a release_change_set object with change_id, files, components, additions, and deletions.
  2. Save the request as JSON with the declared input field and pass the file path to the bundled runner using --input.
  3. Run the operation with an explicit --output-dir; it validates the request and generates or updates a local business artifact.
  4. Receive a release_note_receipt with change_id, title, markdown, and file_count.
  5. If delivery configuration is present, the operation performs its configured business action and returns a delivery receipt. Without configuration, it contacts no external service.

Release Notes Journal Setup

Use Python 3.10 or newer and run the operation from the installed package directory. Create a JSON request containing release_change_set, then provide its path and an output directory:

python scripts/run.py --input examples/request.json --output-dir ./workspace

The bundled example demonstrates the expected input shape. No third-party Python dependencies are required. To enable real delivery, configure the applicable delivery target: CLAWHUB_SMTP_HOST, CLAWHUB_SMTP_PORT, and CLAWHUB_MAIL_FROM for message sends; CLAWHUB_DELIVERY_ENDPOINT for registration or submission; or supply an explicit --delivery-config JSON file. Without delivery configuration, the operation only writes locally.

Release Notes Journal Data Schema & Taxonomy

Input: release_change_set

Field Purpose
change_id Identifies the change set.
files Lists files associated with the change.
components Identifies affected components.
additions Describes additions in the change set.
deletions Describes deletions in the change set.

Output: release_note_receipt

Field Purpose
change_id Carries the change-set identifier into the receipt.
title Provides the release-note title.
markdown Contains the release note in Markdown.
file_count Reports the number of files represented.

The operation creates or updates a local business artifact beneath the explicitly supplied --output-dir. Its implementation is scripts/operation.py; input and output validation are in scripts/validation.py; role configuration is in scripts/config.json. Bundled example values and configured local records support reproducibility.

Release Notes Journal Advanced Features

  • Supports optional real delivery when an SMTP, delivery endpoint, or explicit delivery configuration is provided.
  • Returns a delivery receipt when it performs a configured external business action.
  • Defaults to local-only artifact creation and makes no external contact without delivery configuration.
  • Uses standard-library-only Python dependencies and validates declared input and output fields.
  • Reports command output; a nonzero exit code indicates that the operation failed.

SKILL.md


Loading

METADATA

Github Stars: 0
forks: 0

Featured*