القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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`.
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.
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.
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.
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.
| 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. |
Cut a new release of foolery.
main, not from a feature branch or implementation worktree.main before previewing or running gates.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.