From a4dcbb6bef79d36767429145bd4d798a0c438958 Mon Sep 17 00:00:00 2001 From: YeonGyu-Kim Date: Sun, 24 May 2026 15:07:33 +0900 Subject: [PATCH] docs(publish): use Jobdori bot for releases --- .agents/skills/publish/SKILL.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/.agents/skills/publish/SKILL.md b/.agents/skills/publish/SKILL.md index 1b95b4b73..505bbca72 100644 --- a/.agents/skills/publish/SKILL.md +++ b/.agents/skills/publish/SKILL.md @@ -291,23 +291,25 @@ After the release notes are finalized, post them to the Discord channel. This st The workflow is not complete until this step has either: 1. Sent a Discord message successfully and recorded the message ID, or -2. Failed after `agent-discord auth extract` plus one send retry, with the failure reported to the user. +2. Failed after `agent-discordbot auth status` plus one send retry, with the Jobdori bot-token failure reported to the user. Never skip this step because the release summary was awaiting approval. If the user already confirmed the publish, continue through Discord before stopping. -1. Ensure Discord auth is available: +1. Use the Jobdori bot token through `agent-discordbot` for release announcements. This is the required release path; do not use the personal `agent-discord` token unless the bot path is unavailable and the user explicitly approves the fallback. ```bash -agent-discord auth extract +agent-discordbot auth status ``` 2. **Read recent messages** in the channel to match the existing announcement style: ```bash -agent-discord message list 1454708427392680067 --limit 5 +agent-discordbot message list 1454708427392680067 --limit 5 ``` -3. Post the release announcement to channel `1454708427392680067` matching the style of previous announcements. The message should follow this structure: +3. If `agent-discordbot` is unavailable or unauthorized, stop and report that the Jobdori token path failed. Only then may a human decide whether to use `agent-discord`. + +4. Post the release announcement to channel `1454708427392680067` matching the style of previous announcements. The message should follow this structure: ``` @here @@ -329,7 +331,7 @@ Plus {summary of remaining changes}. ```bash RELEASE_URL=$(gh release view "v${NEW_VERSION}" --json url --jq '.url') -agent-discord message send 1454708427392680067 "{your message following the style above}" +agent-discordbot message send 1454708427392680067 "{your message following the style above}" ``` If the message fails to send, warn the user and continue — do NOT block the publish workflow on Discord errors.