@fitlab-ai/agent-infra 0.11.5 → 0.11.6

package/templates/.agents/skills/create-release-note/SKILL.en.md

@@ -53,6 +53,7 @@ agent-infra-internal platform-release-notes context \
 
 **Purpose**:
 - Part A: Analyze the section structure, heading style, emoji usage, and item format from the latest 3 historical release notes
+- Each `history` item contains a tag, body, and Release URL; use the body as a format sample, not as current change facts
 - Part B: Provide a static complete category list so no existing category is omitted
 - This static list ensures existing category names are not missed during classification; if the current release has no entries for a category, Step 7 still omits the empty section
 - When generating release notes in Step 7, **must** follow both the historical format style and the full category list gathered in Step 3
@@ -60,7 +61,7 @@ agent-infra-internal platform-release-notes context \
 
 ### 4. Collect Merged PRs and Contributors
 
-Use `pullRequests` and `commits` from Step 3. Each commit's `authors` are normalized platform facts containing the git author and co-authors; the skill does not interpret raw platform fields or email rules.
+Use `pullRequests` and `commits` from Step 3. Each commit's `authors` contains only that commit's platform authors; `pullRequestNumbers` records the platform's PR associations. The skill does not interpret raw platform fields or email rules. A PR's `closingIssues` contains its actual closing Issues; never infer a relationship from matching PR and Issue numbers.
 
 ### 5. Collect Related Issues
 
@@ -79,31 +80,36 @@ Use each PR's `closingIssues` from Step 3. Do not parse platform-specific refere
 
 ### 7. Generate Release Notes
 
-**Prioritize the historical format style obtained in Step 3 and ensure all categories listed in Step 3 are covered.** If historical release notes exist, strictly follow their section structure, heading style (including emojis), item format, and bilingual layout.
+**Prioritize the historical format style obtained in Step 3 and ensure all categories listed in Step 3 are covered.** Dynamically use the latest 3 published notes each time. Treat sections, bilingual layout, and installation instructions shared by those notes as stable format; allow item content to vary by release. Never copy an example's authors or links into the current release.
 
 If no historical release notes exist, use the following default Markdown format:
 
 ```markdown
-## {Module/Platform Name}
+## {Module / 模块}
 
-### Enhancement
+### Enhancement / 增强
 
 - [{scope}] Description by @author in [#N](url)
 
-### Bugfix
+### Bugfix / 修复
 
 - [{scope}] Description by @author in [#N](url)
 
-## Contributors
+## Contributors / 贡献者
 
 @contributor1, @contributor2, @contributor3, @reporter1 (reported #N)
+
+## Installation / 安装
+
+{English and Chinese installation instructions for this release, following stable steps in historical notes}
 ```
 
 **Format rules**:
-1. Item format: `- [scope] Description by @author in [#N](url)`
-2. Issue + PR: `in [#Issue](url) and [#PR](url)`
-3. Description: Use PR title, remove `type(scope):` prefix, capitalize first letter
-4. **Contributor collection**:
+1. PR item format: `- [scope] Description by @author in [#N](url)`
+2. Issue + PR: `in [#Issue](url) and [#PR](url)`; Issue reporters come from that PR's `closingIssues`
+3. Render each commit with an empty `pullRequestNumbers` as a standalone item using its subject and resolvable author; link to the commit itself when its URL is available, without adding an Issue or PR link
+4. Description: Use the PR title or commit subject; remove `type(scope):` from PR titles and capitalize the first letter
+5. **Contributor collection**:
    - **Data sources**:
      - PR authors from the typed context
      - Commit co-authors from the typed context's commit `authors`
@@ -123,7 +129,7 @@ If no historical release notes exist, use the following default Markdown format:
      - Reporter-only contributors use the format `@login (reported #N)`; if the same reporter reported multiple Issues, use `@login (reported #N1, #N2)`
      - Reporters are appended after code contributors in the Contributors section, separated by commas
      - Sort reporters by reported Issue count descending, then lexicographically by login for ties
-5. Empty sections: Omit sections with no entries
+6. Empty sections: Omit categories with no entries; retain bilingual headings and the installation section from the historical format
 
 ### 8. Stage, Present, and Confirm
 

package/templates/.agents/skills/create-release-note/SKILL.zh-CN.md

@@ -53,6 +53,7 @@ agent-infra-internal platform-release-notes context \
 
 **用途**：
 - Part A：分析最近 3 条历史发布说明的章节结构、标题风格、emoji 使用、条目格式
+- 每项 `history` 含 tag、正文和 Release URL；正文只作为格式样例，不作为当前版本的变更事实
 - Part B：提供静态完整分类清单，确保后续生成时不遗漏已有分类
 - 该静态清单用于确保变更分类时不遗漏已有类别名称；若当前版本无该类变更，仍按步骤 7 的格式规则省略空分类
 - 后续步骤 7 生成发布说明时，**必须**同时参考步骤 3 的历史格式风格和完整分类清单，保持版本间的一致性
@@ -60,7 +61,7 @@ agent-infra-internal platform-release-notes context \
 
 ### 4. 收集已合并的 PR 与贡献者
 
-使用步骤 3 返回的 `pullRequests` 与 `commits`。每个 commit 的 `authors` 已按平台事实规范化并包含 git author 与 co-author；技能不读取平台原始字段或邮箱规则。
+使用步骤 3 返回的 `pullRequests` 与 `commits`。每个 commit 的 `authors` 只包含该 commit 的平台作者；`pullRequestNumbers` 表示平台记录的 PR 关联。技能不读取平台原始字段或邮箱规则。PR 的 `closingIssues` 是该 PR 实际关闭的 Issue，不按 PR/Issue 编号推断关联。
 
 ### 5. 收集关联 Issue
 
@@ -79,31 +80,36 @@ agent-infra-internal platform-release-notes context \
 
 ### 7. 生成发布说明
 
-**优先使用步骤 3 中获取的历史格式风格，并确保覆盖步骤 3 列出的所有分类。** 如果存在历史发布说明，严格沿用其章节结构、标题风格（含 emoji）、条目格式和双语布局。
+**优先使用步骤 3 中获取的历史格式风格，并确保覆盖步骤 3 列出的所有分类。** 每次动态参考最近 3 条已发布说明；把这些正文共同使用的章节、双语布局和安装段作为稳定格式，条目内容按当前版本变化。不要把样例中的作者或链接复制到当前版本。
 
 如果没有历史发布说明，使用以下默认格式化为 Markdown：
 
 ```markdown
-## {模块/平台名称}
+## {Module / 模块}
 
-### Enhancement
+### Enhancement / 增强
 
 - [{scope}] Description by @author in [#N](url)
 
-### Bugfix
+### Bugfix / 修复
 
 - [{scope}] Description by @author in [#N](url)
 
-## Contributors
+## Contributors / 贡献者
 
 @contributor1, @contributor2, @contributor3, @reporter1 (reported #N)
+
+## Installation / 安装
+
+{本版本的中英文安装说明，沿用历史正文中的稳定安装步骤}
 ```
 
 **格式规则**：
-1. 条目格式：`- [scope] Description by @author in [#N](url)`
-2. Issue + PR：`in [#Issue](url) and [#PR](url)`
-3. 描述：使用 PR 标题，移除 `type(scope):` 前缀，首字母大写
-4. **贡献者搜集**：
+1. PR 条目格式：`- [scope] Description by @author in [#N](url)`
+2. Issue + PR：`in [#Issue](url) and [#PR](url)`；Issue reporter 来自该 PR 的 `closingIssues`
+3. `pullRequestNumbers` 为空的 commit 单独作为条目，使用 commit subject 和可解析作者；有 commit URL 时链接 commit 本身，不添加 Issue/PR 链接
+4. 描述：使用 PR 标题或 commit subject；移除 PR 标题中的 `type(scope):` 前缀，首字母大写
+5. **贡献者搜集**：
    - **数据源**：
      - PR author：来自 `.agents/rules/release-commands.md` 中已合并 PR 查询规则
      - Commit co-authors：来自步骤 3 typed context 的 commit `authors`
@@ -123,7 +129,7 @@ agent-infra-internal platform-release-notes context \
      - 仅报告贡献的用户以 `@login (reported #N)` 格式展示；同一 reporter 报告多个 Issue 时使用 `@login (reported #N1, #N2)`
      - Reporter 在 Contributors 段落中排在代码贡献者之后，以逗号分隔追加
      - Reporter 之间按报告的 Issue 数量降序排列，数量相同时按 login 字典序
-5. 空部分：省略没有条目的部分
+6. 空部分：省略没有条目的分类；保留历史格式中的双语章节与安装段
 
 ### 8. Stage、展示并确认