Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

ship-release

Estrellas51

Forks4

Actualizado11 de mayo de 2026 a las 11:59

Cut a new release of foolery by confirming the version bump, syncing the release branch, previewing changes since the last tag, running quality gates, and publishing verified release artifacts.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

acartine

acartine/foolery

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	ship-release
description	Cut a new release of foolery by confirming the version bump, syncing the release branch, previewing changes since the last tag, running quality gates, and publishing verified release artifacts.

/ship-release

Cut a new release of foolery.

Principles

Release from main, not from a feature branch or implementation worktree.
Keep the worktree clean before starting.
Sync main before previewing or running gates.
Do not use a PR workflow unless the user explicitly requests one.
Do not manually recover by pushing ad hoc commits, tags, or GitHub releases. If the release path fails, fix the release script or the failing gate first.

Steps

Determine bump type — Ask whether this is a patch, minor, or major release unless already specified, for example /ship-release patch. Show the current version and what each bump would produce.
Preflight and sync — Confirm the repo is on main, clean, and current:
```
git status --short --branch
git fetch origin main --tags
git pull --ff-only
```
If git pull --ff-only changes main, continue from the updated commit. If it fails because the branch diverged or the worktree is dirty, stop and report the exact remediation.
Preview changes — After syncing, run:
```
git log $(git describe --tags --abbrev=0)..HEAD --oneline
```
Present a brief summary so the user can confirm what is shipping.
Run quality gates — Execute in parallel:
```
bun run lint
bunx tsc --noEmit
bun run test
bun run build
```
If any gate fails, stop and report. Do not proceed with a broken release.
Cut the release — Run:
```
bun run release -- --<bump_type> --wait-for-artifacts
```
The release script performs its own final branch preflight, release quality gates, atomic branch/tag push, GitHub Release creation, artifact workflow wait, and asset verification. If main moves during the final push, the script rebases the release commit onto the updated upstream, reruns the release quality gates, retags, and retries the atomic push.
Report — Show the new version, link to the GitHub Release, and confirm the runtime tarballs and .sha256 files are available.

Más de este repositorio

mismo repositorio

knots-create

acartine/foolery

Use the Knots workflow through `kno` when asked to create a new knot from a rough request and you need a concise goal, exact acceptance criteria, and repeatable verification steps.

2026-06-1851

knots-e2e

acartine/foolery

Use the Knots workflow through `kno` when asked to drive a knot end to end, run a claimed knot to completion, or keep advancing a knot until it reaches a terminal state such as `SHIPPED`, or a passive waiting state such as `BLOCKED` or `DEFERRED`.

2026-06-1851

knots-plan-orchestrator

acartine/foolery

Use the Knots workflow through `kno` when asked to orchestrate an execution plan from start to finish, processing waves sequentially, steps within each wave sequentially, and launching knots within each step concurrently.

2026-06-1851

knots

acartine/foolery

Use the Knots workflow through `kno` when asked to create a knot, work on a specific knot, claim or execute a knot, advance a knot to its next state, or recover or roll back a knot safely after blocked or failed work.

2026-06-1851

foolery-configure

acartine/foolery

Configure Foolery by writing a validated ~/.config/foolery/settings.toml and ~/.config/foolery/registry.json. Triggers: `foolery setup`, "configure foolery", "add an agent", "remove an agent", "change dispatch pools", "mount a repo". Works from any frontier agent (Claude, Codex, OpenCode, Gemini, Copilot) — use plain shell verbs, not harness-specific tooling.

2026-04-2151

investigate-foolery-leases

acartine/foolery

Investigate Foolery lease, session, and server logs when asked why an agent turn failed to advance, rolled back unexpectedly, hung, leaked a lease, or skipped lease usage. Use this for the dev server on port 3000, the installed runtime on port 3210, and recent 24-48 hour forensic reviews across both log roots.

2026-04-0751

/ship-release

Cut a new release of foolery.

Principles

Release from main, not from a feature branch or implementation worktree.

Keep the worktree clean before starting.

Sync main before previewing or running gates.

Do not use a PR workflow unless the user explicitly requests one.

Do not manually recover by pushing ad hoc commits, tags, or GitHub releases. If the release path fails, fix the release script or the failing gate first.

Steps

Determine bump type — Ask whether this is a patch, minor, or major release unless already specified, for example /ship-release patch. Show the current version and what each bump would produce.

Preflight and sync — Confirm the repo is on main, clean, and current:

git status --short --branch
git fetch origin main --tags
git pull --ff-only

If git pull --ff-only changes main, continue from the updated commit. If it fails because the branch diverged or the worktree is dirty, stop and report the exact remediation.

Preview changes — After syncing, run:

git log $(git describe --tags --abbrev=0)..HEAD --oneline

Present a brief summary so the user can confirm what is shipping.

Run quality gates — Execute in parallel:

bun run lint
bunx tsc --noEmit
bun run test
bun run build

If any gate fails, stop and report. Do not proceed with a broken release.

Cut the release — Run:

bun run release -- --<bump_type> --wait-for-artifacts

The release script performs its own final branch preflight, release quality gates, atomic branch/tag push, GitHub Release creation, artifact workflow wait, and asset verification. If main moves during the final push, the script rebases the release commit onto the updated upstream, reruns the release quality gates, retags, and retries the atomic push.

Report — Show the new version, link to the GitHub Release, and confirm the runtime tarballs and .sha256 files are available.