docs: keep developer tooling out of release tweets · openclaw/openclaw@3c8050c
steipete
·
2026-05-20
·
via Recent Commits to openclaw:main
File tree
.agents/skills/openclaw-release-maintainer
| Original file line number | Diff line number | Diff line change |
|---|
@@ -173,6 +173,10 @@ live`; keep it clearly beta and avoid implying stable promotion.
|
173 | 173 | - Do not feature QA parity, test coverage, release gates, or validation lanes in |
174 | 174 | user-facing launch tweets. Keep them for release notes or maintainer proof |
175 | 175 | unless the operator explicitly asks for validation-focused copy. |
| 176 | +- Do not feature plugin-author or developer tooling such as SDK helpers, |
| 177 | + tool-plugin scaffolding, build/validate/init commands, or internal CLI |
| 178 | + plumbing in general user-facing launch tweets unless the operator explicitly |
| 179 | + asks for developer-focused copy. |
176 | 180 | - Tone: high-signal, slightly cheeky, confident, not corporate. One joke is |
177 | 181 | enough. Avoid punching down, insulting users, or promising what was not |
178 | 182 | verified. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
