菜单
Post a structured Linear project update document on a version release. Orchestrates tapps_release_update → docs_validate_release_update → save_document → cache invalidation. Use when posting a release announcement to Linear after shipping a new version.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Persistent cross-session memory + knowledge graph for AI coding agents. Use when you need to recall prior decisions before making a non-trivial choice, save the rationale behind a decision so it survives the session, share findings across agents in a project (Hive), or record an experience event / KG triple. Talk to the deployed brain at http://127.0.0.1:8080/mcp/ via MCP tools — never via raw psycopg.
Frontend work flow combining UX playbook and standard finish pipeline. Use when the task is primarily UI/UX implementation or accessibility.
Write a structured cross-session handoff and close the TAPPS session lifecycle so the next chat can continue without a long paste. Use when ending a session, handing off to a fresh chat, or the user says hand off, save session state, or continue next time.
Frontend work flow combining UX playbook and standard finish pipeline. Use when the task is primarily UI/UX implementation or accessibility.
Write a structured cross-session handoff and close the TAPPS session lifecycle so the next chat can continue without a long paste. Use when ending a session, handing off to a fresh chat, or the user says hand off, save session state, or continue next time.
Persistent cross-session memory + knowledge graph for AI coding agents. Use when you need to recall prior decisions before making a non-trivial choice, save the rationale behind a decision so it survives the session, share findings across agents in a project (Hive), or record an experience event / KG triple. Talk to the deployed brain at http://127.0.0.1:8080/mcp/ via MCP tools — never via raw psycopg.
| name | linear-release-update |
| user-invocable | true |
| model | claude-haiku-4-5-20251001 |
| description | Post a structured Linear project update document on a version release. Orchestrates tapps_release_update → docs_validate_release_update → save_document → cache invalidation. Use when posting a release announcement to Linear after shipping a new version. |
| allowed-tools | mcp__nlt-release-ship__tapps_release_update mcp__nlt-release-ship__docs_generate_release_update mcp__nlt-release-ship__docs_validate_release_update mcp__nlt-release-ship__docs_release_gate mcp__plugin_linear_linear__save_document mcp__nlt-linear-issues__tapps_linear_snapshot_invalidate |
| argument-hint | --version vX.Y.Z --prev-version vX.Y.W [--team <team>] [--project <project>] [--dry-run] |
Post a structured Linear project update document when a new version is released. The user's request to post a release update is standing authorization for the full pipeline — do NOT pause mid-flow to ask "should I post this?"
Flow:
mcp__nlt-release-ship__tapps_release_update(version, prev_version, team, project).
version and prev_version are required. Parse from the user's prompt or ask once if both are missing.team and project: read from .tapps-mcp.yaml if present (linear_team, linear_project fields), otherwise pass empty strings.dry_run=true is requested, pass it through — the tool returns the body without requiring validation to pass.1b. Docs release gate (required unless dry_run): Call mcp__nlt-release-ship__docs_release_gate. If success=false or aggregate verdict is fail, surface findings and stop — do not post.
Check the response:
success=false: surface the error.message and findings to the user. Stop — do not post.agent_ready=false (and not dry_run): surface findings, stop.agent_ready=true: proceed.Call mcp__plugin_linear_linear__save_document:
project: use data.project from the tool response.title: use data.document_title from the tool response (format: Release vX.Y.Z — YYYY-MM-DD).content: use data.body from the tool response verbatim.After save_document succeeds, call mcp__nlt-linear-issues__tapps_linear_snapshot_invalidate:
team: use data.team from tool response.project: use data.project from tool response.Report the document URL from save_document response and the version that was posted.
Rules:
save_document without a prior agent_ready=true from tapps_release_update (unless dry_run=true).document_title must use the em-dash format from data.document_title — do not construct it manually.data.body verbatim.