Run any Skill in Manus with one click

pre-release-test

Stars113

Forks2

UpdatedMay 19, 2026 at 20:04

Use when preparing a Herald beta release, checking release readiness, or running broad deterministic integration gates across TUI themes, inline images, SSH, and MCP before tagging.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

herald-email

herald-email/herald-mail-app

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

3 files

SKILL.md

readonly

name	pre-release-test
description	Use when preparing a Herald beta release, checking release readiness, or running broad deterministic integration gates across TUI themes, inline images, SSH, and MCP before tagging.

Pre-Release Test

Use this skill before cutting a Herald beta or after risky UI/media/theme changes. It is a deterministic demo-data gate and does not touch live IMAP.

Default Gate

Run from the repository root:

.agents/skills/pre-release-test/scripts/run_pre_release_gate.sh

The runner writes one report directory under reports/pre-release-gate_<timestamp>/ and exits nonzero if any required gate fails.

What It Covers

Go verification: make test, make vet.
Release binaries: make build build-ssh build-mcp.
TUI visuals: themed demo captures at 220x50, 80x24, and 50x15.
Inline images: custom ttyd browser-raster probes with no app theme and with HERALD_THEME=jade-signal.
SSH: demo-mode server startup and local SSH connection smoke.
MCP: demo-mode tools/list stdio smoke.

Useful Overrides

HERALD_PRE_RELEASE_THEME=solar-paper \
HERALD_PRE_RELEASE_IMAGE_PROTOCOL=iterm2 \
HERALD_PRE_RELEASE_PORT_BASE=7780 \
  .agents/skills/pre-release-test/scripts/run_pre_release_gate.sh

Use a different HERALD_PRE_RELEASE_PORT_BASE if local ttyd or SSH ports are busy.

Rules

Do not replace this with stock ttyd; custom ttyd raster proof is the required image gate.
If the runner fails because a local dependency is missing, install or configure that dependency and rerun instead of marking the release ready.
If a native iTerm2, Ghostty, or Kitty placement claim matters, add manual screenshots to the report directory; native evidence is additive, not a substitute for the scripted gate.

More from this repository

same repository

release

herald-email/herald-mail-app

Herald beta release workflow for requests to cut, tag, publish, or repair a Herald release. Use when Codex should read RELEASE.md, review changes since the last tag, recommend the next v0.X.Y-beta.Z version, update What's New docs pages, create and push an annotated tag, monitor CI/CD, fix release blockers, move or supersede the tag when appropriate, and write release notes.

2026-06-24113

herald-autopilot

herald-email/herald-mail-app

Use when you want one repo-local Herald workflow to take a single bug, feature, or workflow improvement from intake through planning, isolated worktree setup, implementation, impact-based verification, branch handoff, and GEPA-style run logging.

2026-06-07113

finish-development

herald-email/herald-mail-app

Herald-specific completion workflow for requests such as "finish-development", "nice" as a repo completion command, "wrap this branch", "fast merge", "fastpass", "quick merge", "fast mode", or "commit, merge to main, delete worktree". Use when a completed Herald task should be polished or fast-passed, committed, merged into main, and its feature worktree cleaned up.

2026-06-06113

tui-test

herald-email/herald-mail-app

Battle-test terminal UIs such as Herald via tmux and ttyd: reset states, compare visible hotkeys with actual behavior, capture ANSI/PNG evidence, run resize soaks, and verify terminal raster image previews.

2026-05-29113

approve-gepa-changes

herald-email/herald-mail-app

Use when approving, rejecting, or marking implemented Herald GEPA pending approval items, including requests like "approve GEPA changes", "approve all pending GEPA", or approval of a specific queue key from docs/superpowers/gepa-pending-approvals.md.

2026-05-08113

tui-test

herald-email/herald-mail-app

Battle-test the Herald TUI — automated exploratory testing that captures screens, detects visual defects programmatically, and digs into anything suspicious. Simulates prolonged real usage.

2026-04-04113

name	pre-release-test
description	Use when preparing a Herald beta release, checking release readiness, or running broad deterministic integration gates across TUI themes, inline images, SSH, and MCP before tagging.

Pre-Release Test

Use this skill before cutting a Herald beta or after risky UI/media/theme changes. It is a deterministic demo-data gate and does not touch live IMAP.

Default Gate

Run from the repository root:

.agents/skills/pre-release-test/scripts/run_pre_release_gate.sh

The runner writes one report directory under reports/pre-release-gate_<timestamp>/ and exits nonzero if any required gate fails.

What It Covers

Go verification: make test, make vet.
Release binaries: make build build-ssh build-mcp.
TUI visuals: themed demo captures at 220x50, 80x24, and 50x15.
Inline images: custom ttyd browser-raster probes with no app theme and with HERALD_THEME=jade-signal.
SSH: demo-mode server startup and local SSH connection smoke.
MCP: demo-mode tools/list stdio smoke.

Useful Overrides

HERALD_PRE_RELEASE_THEME=solar-paper \
HERALD_PRE_RELEASE_IMAGE_PROTOCOL=iterm2 \
HERALD_PRE_RELEASE_PORT_BASE=7780 \
  .agents/skills/pre-release-test/scripts/run_pre_release_gate.sh

Use a different HERALD_PRE_RELEASE_PORT_BASE if local ttyd or SSH ports are busy.

Rules

Do not replace this with stock ttyd; custom ttyd raster proof is the required image gate.
If the runner fails because a local dependency is missing, install or configure that dependency and rerun instead of marking the release ready.
If a native iTerm2, Ghostty, or Kitty placement claim matters, add manual screenshots to the report directory; native evidence is additive, not a substitute for the scripted gate.