메뉴
Succinct release-needed signal and manual release-cut workflow for Farmslot workspaces (Command Center, gateway, protocol, companion, npm packages). Run release-status first; curate Unreleased bullets; cut with reviewed proposal.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Drive another model through a tmux pane with guardrails. Use when Codex should orchestrate Claude, Codex, Grok, Cursor, or another agent inside an existing tmux session, verify pane state before sending input, and keep a feedback loop around observed pane output.
Build a validation recipe from PR intent, ticket ACs, or investigation findings
Help run or install a local recipe runtime without assuming the full Farmslot framework
Author or review a Farmslot backlog spec (.backlog/specs/**) — run deterministic spec-lint, check AC↔scope traceability and code refs, then file via backlog.create with the spec attached and verify the round-trip. For agents filing work the farm will later dispatch.
Review validation recipes and evidence quality without project-specific assumptions
Communicate complex agent output as compact, reviewable Farmslot operator packets with artifact anchors and safe action requests
| name | fs-release-cut |
| description | Succinct release-needed signal and manual release-cut workflow for Farmslot workspaces (Command Center, gateway, protocol, companion, npm packages). Run release-status first; curate Unreleased bullets; cut with reviewed proposal. |
Developer tool for when to cut a release and how to finalize changelogs in the Farmslot monorepo.
Not part of slot lifecycle or dispatch. Use before hosted CC deploys, Companion EAS updates, or npm publishes.
From a Farmslot checkout:
yarn release:status
Read the one-line verdict per group:
| Verdict | Meaning |
|---|---|
NO | Only placeholders or nothing meaningful in ## Unreleased |
SOON | A few bullets; wait for the current PR batch to land |
YES | Operator-facing changes ready — cut before deploy/announce |
Pick a release group:
hosted-cc — Command Center UI, gateway, protocolcompanion — Mobile Companionnpm — published packagesGenerate a proposal (rule-based split + operator summaries):
yarn release:cut --group hosted-cc --assist
Review .release-cut/proposal.json:
include — bullets that ship in this releasedefer — internal/chore bullets that stay in ## UnreleasedoperatorSummary — 3–5 lines for What's New UIEdit the JSON when the heuristic mis-classified items. Use your judgment to consolidate duplicates and rewrite for operators.
After the proposal looks right:
yarn release:cut --group hosted-cc --from-proposal .release-cut/proposal.json --execute
This bumps workspace versions, finalizes changelog sections, writes release-notes.json, and syncs PROTOCOL_VERSION when protocol is in the group.
Commit separately:
chore(release): cut command-center-ui@X.Y.Z, gateway@X.Y.Z, …
| Group | Next step |
|---|---|
hosted-cc | Merge PR → docs-site.yml deploys farmslot.io/cc with What's New |
companion | bash apps/companion/scripts/release/release.sh --execute (after cut) |
npm | yarn packages:publish:check:strict then manual yarn npm publish per package |
Any PR that changes workspace code must add a non-placeholder bullet under that workspace's ## Unreleased. CI enforces via yarn quality:changelogs:pr.
--execute without reviewing .release-cut/proposal.json.