skills.rest
graysurf
graysurfCOMMUNITY
Explore all skills by this author →
GitHub

release

Execute repository-owned release scripts at .agents/scripts/release.sh.

Updated Aug 27, 2026
Search Tags:#automation#workflow#versioning#build#repository#release#script
One-click install
npx skills add https://github.com/graysurf/agent-runtime-kit --skill release-graysurf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/graysurf/agent-runtime-kit/tree/main/tests/golden/claude/plugins/meta/skills/release/expected
Command: npx skills add https://github.com/graysurf/agent-runtime-kit --skill release-graysurf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatch release requests to a repository-owned .agents/scripts/release.sh implementation.

Core Features & Use Cases

  • Dispatch a release command to a project-local script located at .agents/scripts/release.sh.
  • Validate prereqs like repository root, script existence, and executability, and produce clear release evidence.
  • Provide a defined workflow boundary between Runtime Kit and consuming repositories.

Quick Start

Run agent-run from the repository root to execute the local .agents/scripts/release.sh script.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version releases using a repository-local script?▼

To automate version releases, this Skill dispatches release requests to a repository-owned .agents/scripts/release.sh script. It validates the script's existence and executability to ensure predictable behavior and traceable results across target repositories.

What is a repo-local release script and when do I need one?▼

A repo-local release script is an executable file at .agents/scripts/release.sh that handles project-specific versioning. You need one when requiring a defined workflow boundary between your runtime environment and consuming repositories for traceable release execution.

How do I execute a release dispatch from the repository root?▼

To execute a release dispatch, run agent-run from the repository root. This triggers the local .agents/scripts/release.sh implementation, enforcing prerequisites and surfacing release evidence back to the user.

Do I need a specific file structure to run automated build releases?▼

Yes, you need a repository-owned script located at .agents/scripts/release.sh. The release dispatch validates this file's existence and executability before executing, ensuring predictable behavior and traceable results.

What happens if the release script is missing or not executable?▼

If the release script is missing or not executable, the dispatch enforces failure modes by validating prerequisites and surfacing the error back to the user. This ensures predictable behavior and traceable results before attempting execution.

Why use a repository-owned script for release workflow automation?▼

Using a repository-owned script provides a defined workflow boundary between the runtime kit and consuming repositories. This approach enforces inputs, outputs, and failure modes while validating script existence for traceable release results.

Related Skills

Explore More Software Engineering Skills→
ManuelKugelmannManuelKugelmann
3

check-bash

Validate Bash script syntax without executing the scripts.

Community
Basic
Xpotato1024Xpotato1024
1

devkit-release-maintainer

Validate devkit release metadata across tags, installers, and version outputs.

Community
Advanced
ATTCKDigitalATTCKDigital
50

smith-build

Automate the end-to-end build workflow from requirements to merged PR and release notes.

Official
Advanced
gaelic-ghostgaelic-ghost
6

maintain-project-repo

...

Community
Intermediate