ln-910-community-engagement
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChinesePaths: File paths (,shared/,references/) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.../ln-*
路径说明： 文件路径（、shared/、references/）是相对于技能仓库根目录的。如果在当前工作目录（CWD）中未找到，请定位到本SKILL.md所在目录，然后向上一级即为仓库根目录。../ln-*
ln-910-community-engagement
ln-910-community-engagement
Type: L2 Coordinator (active)
Category: 9XX Community Engagement
Analyzes current community health and repository state, consults the engagement strategy, and delegates to the appropriate worker. Each worker is also invocable standalone.
类型： L2 协调器（激活状态）
分类： 9XX 社区参与
分析当前社区健康状况与仓库状态，参考社区参与策略，并将任务委派给对应的执行worker。每个worker也可单独调用。
Overview
概述
| Aspect | Details |
|---|---|
| Input | |
| Output | Situation report + delegated action via worker skill |
| Workers | ln-911 (triager), ln-912 (announcer), ln-913 (debater) |
| 维度 | 详情 |
|---|---|
| 输入 | |
| 输出 | 情况报告 + 通过worker技能执行的委派操作 |
| 执行Worker | ln-911（分类员）、ln-912（发布员）、ln-913（辩论员） |
Phase 0: GitHub Discovery
阶段0：GitHub 信息发现
MANDATORY READ: Load
references/github_discovery.mdExecute the discovery protocol. Extract:
- for all GitHub operations
{owner}/{repo} - for GraphQL mutations (passed to workers)
repo.id - login (authenticated user)
maintainer - Discussion category IDs
Gate checks: gh authenticated? Discussions enabled?
Load strategy: check in target project, fallback to .
docs/community_engagement_strategy.mdreferences/community_strategy_template.md必读要求： 加载
references/github_discovery.md执行信息发现协议，提取以下内容：
- 所有GitHub操作对应的
{owner}/{repo} - 用于GraphQL变更的 （将传递给worker）
repo.id - 维护者登录账号（已认证用户）
- 讨论分类ID
准入检查： 是否已通过GitHub认证？是否启用了讨论功能？
加载策略：检查目标项目中的 ，若不存在则回退使用 。
docs/community_engagement_strategy.mdreferences/community_strategy_template.mdPhase 1: Situation Analysis
阶段1：情况分析
If contains a direct action keyword (, , ), skip analysis and jump to Phase 3 (Direct Delegation).
$ARGUMENTSannouncedebatetriageOtherwise, gather context from multiple sources in parallel:
若 包含直接操作关键词（、、），则跳过分析，直接进入阶段3（直接委派）。
$ARGUMENTSannouncedebatetriage否则，从多源并行收集上下文信息：
1a. Community Health
1a. 社区健康状况
Delegate to triager in summary mode (no interactive preview):
Skill(skill: "ln-911-github-triager", args: "summary")Extract from triager output: red flags, priority counts (P0/P1/P2), health metrics.
以摘要模式委派给分类员（无交互式预览）：
Skill(skill: "ln-911-github-triager", args: "summary")从分类员输出中提取：风险预警项、优先级计数（P0/P1/P2）、健康指标。
1b. Unreleased Changes
1b. 未发布变更
bash
undefinedbash
undefinedLast announcement date: most recent Announcements discussion
上次发布日期：最新的Announcements讨论时间
gh api graphql -f query='query($owner: String!, $name: String!) {
repository(owner: $owner, name: $name) {
discussions(first: 1, categoryId: "{categories.Announcements}", orderBy: {field: CREATED_AT, direction: DESC}) {
nodes { createdAt title }
}
}
}' -f owner="{owner}" -f name="{repo}"
Then check what changed since:
```bash
git log --oneline --since="{last_announcement_date}"Read — any entries newer than the last announcement?
CHANGELOG.mdgh api graphql -f query='query($owner: String!, $name: String!) {
repository(owner: $owner, name: $name) {
discussions(first: 1, categoryId: "{categories.Announcements}", orderBy: {field: CREATED_AT, direction: DESC}) {
nodes { createdAt title }
}
}
}' -f owner="{owner}" -f name="{repo}"
然后检查自该日期以来的变更：
```bash
git log --oneline --since="{last_announcement_date}"查看 —— 是否有比上次发布更新的条目？
CHANGELOG.md1c. Cadence Check
1c. 节奏检查
From strategy Section 4:
- Days since last announcement → monthly digest overdue if >30 days?
- Any pending architectural decisions that need RFC?
参考策略第4节：
- 距离上次发布已过去的天数 → 若超过30天，月度摘要是否逾期？
- 是否有需要提交RFC的待决架构决策？
Phase 2: Decision Matrix
阶段2：决策矩阵
Apply strategy Section 1 (Announcement vs Debate) to the gathered context:
| Condition | Priority | Action | Worker |
|---|---|---|---|
| Red flags: unanswered discussions >7d | P0 | List items needing response (no worker — direct action) | Recommendations only |
| Red flags: PRs needing review | P0 | List PRs needing review | Recommendations only |
| Unreleased changes in CHANGELOG | P1 | Announce: new features/fixes | → ln-912 |
| P1 | Debate: launch RFC | → ln-913 |
| Monthly digest overdue (>30d) | P2 | Monthly digest announcement | → ln-912 |
| Design questions identified in Phase 1 | P2 | Debate: RFC for open decisions | → ln-913 |
| Community health OK, nothing unreleased | — | Report "all clear" | No delegation |
根据收集到的上下文，应用策略第1节（发布 vs 辩论）：
| 条件 | 优先级 | 操作 | 执行Worker |
|---|---|---|---|
| 风险预警：未回复讨论超过7天 | P0 | 列出需要回复的事项（无worker —— 直接操作） | 仅提供建议 |
| 风险预警：需要审核的PR | P0 | 列出需要审核的PR | 仅提供建议 |
| CHANGELOG中有未发布变更 | P1 | 发布：新功能/修复内容 | → ln-912 |
| P1 | 辩论：发起RFC | → ln-913 |
| 月度摘要逾期（>30天） | P2 | 发布月度摘要 | → ln-912 |
| 阶段1中识别出设计问题 | P2 | 辩论：针对待决决策发起RFC | → ln-913 |
| 社区健康状况良好，无未发布变更 | — | 报告“一切正常” | 无需委派 |
Output: Situation Report
输出：情况报告
Present to user:
undefined向用户展示：
undefinedCommunity Status — {YYYY-MM-DD}
社区状态 — {YYYY-MM-DD}
Repo: {owner}/{repo}
Last announcement: {date} ({days} days ago)
Open items: {issues} issues, {prs} PRs, {discussions} discussions
仓库： {owner}/{repo}
上次发布： {date}（{days}天前）
待处理事项： {issues}个问题，{prs}个PR，{discussions}个讨论
Red Flags
风险预警
{list or "None"}
{列表或“无”}
Recommended Action
建议操作
{One of: Announce / Debate / Respond to items / No action needed}
Reason: {brief explanation based on strategy criteria}
**Wait for user approval before proceeding.**
---{选项之一：发布 / 辩论 / 回复事项 / 无需操作}
原因： {基于策略标准的简要说明}
**继续执行前需等待用户确认。**
---Phase 3: Delegate
阶段3：任务委派
After user approves the recommended action:
用户确认建议操作后：
Direct Delegation (when $ARGUMENTS
specifies action)
$ARGUMENTS直接委派（当$ARGUMENTS
指定操作时）
$ARGUMENTS| Argument | Delegation |
|---|---|
| |
| |
| |
| 参数 | 委派方式 |
|---|---|
| |
| |
| |
Analysis-Based Delegation
基于分析的委派
| Recommended action | Delegation |
|---|---|
| Announce | |
| Debate | |
| Respond to items | No delegation — present the list of items needing response with GitHub URLs |
| No action needed | Report status, done |
| 建议操作 | 委派方式 |
|---|---|
| 发布 | |
| 辩论 | |
| 回复事项 | 无需委派 —— 展示需要回复的事项列表及对应的GitHub链接 |
| 无需操作 | 报告状态，流程结束 |
Shared References
共享参考文件
| File | Purpose |
|---|---|
| Phase 0: dynamic repo/category/user discovery |
| Default engagement strategy (fallback) |
| GitHub Discussion formatting rules |
| 文件 | 用途 |
|---|---|
| 阶段0：动态发现仓库/分类/用户信息 |
| 默认参与策略（回退方案） |
| GitHub讨论格式规范 |
Strategy Override
策略覆盖
Each target project can override the default strategy by creating . All skills check project-local first, then fall back to the template in .
docs/community_engagement_strategy.mdreferences/每个目标项目可通过创建 来覆盖默认策略。所有技能会优先检查项目本地的策略文件，若不存在则回退使用目录下的模板。
docs/community_engagement_strategy.mdreferences/Definition of Done
完成标准
- GitHub discovery complete (owner/repo, categories, maintainer extracted)
- Situation analyzed (health + unreleased changes + cadence) OR direct delegation triggered
- Decision matrix applied with priority-based action selection
- Worker delegated or recommendations shown to user
- User informed of outcome
- GitHub信息发现完成（已提取owner/repo、分类、维护者信息）
- 已完成情况分析（健康状况+未发布变更+节奏检查）或已触发直接委派
- 已应用决策矩阵，基于优先级选择操作
- 已委派worker或向用户展示建议
- 已将结果告知用户
Phase 4: Meta-Analysis
阶段4：元分析
MANDATORY READ: Load
shared/references/meta_analysis_protocol.mdSkill type: . Run after Phase 3 completes. Output to chat using the format.
planning-coordinatorplanning-coordinatorVersion: 1.0.0
Last Updated: 2026-03-13
必读要求： 加载
shared/references/meta_analysis_protocol.md技能类型：。阶段3完成后执行，使用格式将输出内容发送至聊天窗口。
planning-coordinatorplanning-coordinator版本： 1.0.0
最后更新日期： 2026-03-13